Senior living engagement and care support platforms

ABSTRACT

Provided herein is an engagement and care support platform (“ECSP”) computer system including at least one processor in communication with at least one memory device for facilitating senior user engagement. The processor is programmed to: (i) register a user through an application, (ii) register a caregiver associated with the user through the application, (iii) generate a senior profile based upon user personal and scheduling data, (iv) build a daily interactive user interface that reflects the senior profile, (v) display the daily interactive user interface at a first client device associated with the user, (vi) cause the first client device to initiate a daily interaction prompt to the user, (vii) determine whether any user interaction was received in response to the daily interaction prompt, and (viii) transmit a daily update message to a second client device associated with the caregiver, including an indication of whether any user interaction was received.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/996,592, filed Aug. 18, 2020, entitled “SENIOR LIVING ENGAGEMENT ANDCARE SUPPORT PLATFORMS,” which claims the benefit of priority to U.S.Provisional Patent Application Ser. No. 63/041,409, filed Jun. 19, 2020,entitled “SENIOR LIVING ENGAGEMENT AND CARE SUPPORT PLATFORMS,” U.S.Provisional Patent Application Ser. No. 62/935,854, filed Nov. 15, 2019,entitled “SENIOR LIVING ENGAGEMENT AND CARE SUPPORT PLATFORMS,” U.S.Provisional Patent Application Ser. No. 62/935,860, filed Nov. 15, 2019,entitled “SENIOR LIVING ENGAGEMENT AND CARE SUPPORT PLATFORMS,” U.S.Provisional Patent Application Ser. No. 62/888,746, filed Aug. 19, 2019,entitled “SENIOR LIVING ENGAGEMENT AND CARE SUPPORT PLATFORMS,” and U.S.Provisional Patent Application Ser. No. 62/892,207, filed Aug. 27, 2019,entitled “SENIOR LIVING ENGAGEMENT AND CARE SUPPORT PLATFORMS,” theentire contents and disclosures of which are hereby incorporated hereinby reference in their entirety.

FIELD OF THE INVENTION

The present disclosure relates to senior living computer platforms and,more particularly, to systems and methods for using a senior livingcomputer platform to facilitate senior engagement with their dailyschedule and caregivers associated with the seniors, and coordinate carebetween caregivers.

BACKGROUND

At least some conventional computer networks have enabled caregivers(e.g., family members, friends, and care service providers) associatedwith senior users to coordinate care for the senior user. However,conventional systems usually merely keep a schedule of the coordinatedcare, and may not provide additional functionality. Further, knownsystems may not facilitate senior engagement in their daily schedules,and may therefore not provide information on such engagement tocaregivers. Known systems may have other drawbacks as well.

BRIEF SUMMARY

The present embodiments may relate to systems and methods forfacilitating senior engagement in their daily schedules and coordinatingcare between caregivers of the senior. The system may include anengagement and care support computing device, one or more clientdevices, one or more third party servers, and/or one or more databases.

In one aspect, an engagement and care support platform computer systemfor facilitating senior user engagement may be provided. The computersystem may include at least one processor in communication with at leastone memory device. The at least one processor may be programmed to: (i)register a user through an application, wherein the user inputs personaland scheduling data into the application, (ii) register a caregiverassociated with the user through the application, (iii) generate asenior profile based upon the user personal and scheduling data, (iv)build a daily interactive user interface that reflects the seniorprofile, (v) display the daily interactive user interface at a firstclient device associated with the user, (vi) cause the first clientdevice to initiate a daily interaction prompt to the user, (vii)determine whether any user interaction was received at the first clientdevice in response to the daily interaction prompt, and (viii) transmita daily update message to a second client device associated with thecaregiver, the daily update message including an indication of whetherany user interaction was received at the first client device. The carecoordination support platform computer system may include additional,less, or alternate functionality, including that discussed elsewhereherein.

In another aspect, a computer-implemented method for facilitating senioruser engagement may be provided. The computer-implemented method may beperformed by an engagement and care support platform computer systemincluding at least one processor in communication with at least onememory device. The computer-implemented method may include: (i)registering a user through an application, wherein the user inputspersonal and scheduling data into the application, (ii) registering acaregiver associated with the user through the application, (iii)generating a senior profile based upon the user personal and schedulingdata, (iv) building a daily interactive user interface that reflects thesenior profile, (v) displaying the daily interactive user interface at afirst client device associated with the user, (vi) causing the firstclient device to initiate a daily interaction prompt to the user, (vii)determining whether any user interaction was received at the firstclient device in response to the daily interaction prompt, and/or (viii)transmitting a daily update message to a second client device associatedwith the caregiver, the daily update message including an indication ofwhether any user interaction was received at the first client device.The method may include additional, less, or alternate actions, includingthose discussed elsewhere herein.

In yet another aspect, a non-transitory computer-readable media havingcomputer-executable instructions embodied thereon may be provided. Whenexecuted by an engagement and care support platform computer systemincluding a processor in communication with a memory device, thecomputer-executable instructions may cause the processor to (i) registera user through an application, wherein the user inputs personal andscheduling data into the application, (ii) register a caregiverassociated with the user through the application, (iii) generate asenior profile based upon the user personal and scheduling data, (iv)build a daily interactive user interface that reflects the seniorprofile, (v) display the daily interactive user interface at a firstclient device associated with the user, (vi) cause the first clientdevice to initiate a daily interaction prompt to the user, (vii)determine whether any user interaction was received at the first clientdevice in response to the daily interaction prompt, and (viii) transmita daily update message to a second client device associated with thecaregiver, the daily update message including an indication of whetherany user interaction was received at the first client device.

BRIEF DESCRIPTION OF THE DRAWINGS

The Figures described below depict various aspects of the systems andmethods disclosed therein. It should be understood that each Figuredepicts an embodiment of a particular aspect of the disclosed systemsand methods, and that each of the Figures is intended to accord with apossible embodiment thereof. Further, wherever possible, the followingdescription refers to the reference numerals included in the followingFigures, in which features depicted in multiple Figures are designatedwith consistent reference numerals.

There are shown in the drawings arrangements which are presentlydiscussed, it being understood, however, that the present embodimentsare not limited to the precise arrangements and are instrumentalitiesshown, wherein:

FIG. 1 illustrates an exemplary engagement and care support computersystem for facilitating engagement of a user and caregivers with a careschedule of the user;

FIG. 2 illustrates an exemplary configuration of an exemplary usercomputing device that may be used in the engagement and care supportcomputer system illustrated in FIG. 1;

FIG. 3 illustrates an exemplary configuration of an exemplary servercomputing device that may be used in the engagement and care supportcomputer system illustrated in FIG. 1;

FIG. 4 illustrates a flow chart of an exemplary computer-implementedmethod implemented by the exemplary engagement and care support computersystem shown in FIG. 1;

FIG. 5 illustrates a diagram of components of one or more exemplarycomputing devices that may be used in the engagement and care supportcomputer system shown in FIG. 1;

FIG. 6 is a screenshot of one example initial welcome page of anengagement and care support application illustrated in FIG. 1;

FIG. 7 is a screenshot of one example user registration page of anengagement and care support application illustrated in FIG. 1;

FIG. 8 is a screenshot of one example caregiver registration page of anengagement and care support application illustrated in FIG. 1;

FIG. 9 is a screenshot of one example welcome page of an engagement andcare support application illustrated in FIG. 1;

FIG. 10 is a screenshot of one example user care team page of anengagement and care support application illustrated in FIG. 1;

FIG. 11A is a screenshot of one example user home page of an engagementand care support application illustrated in FIG. 1;

FIG. 11B is a screenshot of another example user home page of anengagement and care support application illustrated in FIG. 1;

FIGS. 11C-11L are screenshots of example user interaction pages of anengagement and care support application illustrated in FIG. 1;

FIGS. 12A and 12B are screenshots of example caregiver home screens ofan engagement and care support application illustrated in FIG. 1;

FIGS. 13A and 13B are screenshots of further example caregiver homescreens of an engagement and care support application illustrated inFIG. 1;

FIG. 14 is a screenshot of one example caregiver feed page of anengagement and care support application illustrated in FIG. 1;

FIG. 15 is a screenshot of one example caregiver schedule page of anengagement and care support application illustrated in FIG. 1;

FIGS. 16 and 17 are screenshots of example caregiver list pages of anengagement and care support application illustrated in FIG. 1;

FIG. 18 is a screenshot of one example care circle page of an engagementand care support application illustrated in FIG. 1; and

FIG. 19 illustrates an exemplary computer-implemented method ofproviding a care circle platform that includes chatbot and mobileapplication functionality that facilitates coordination of virtual carecircle member communication and tasks.

The Figures depict preferred embodiments for purposes of illustrationonly. One skilled in the art will readily recognize from the followingdiscussion that alternative embodiments of the systems and methodsillustrated herein may be employed without departing from the principlesof the invention described herein.

DETAILED DESCRIPTION

The present embodiments may relate to, inter alia, systems and methodsfor facilitating engagement of a senior user (also referred to herein asa “user”) in a care schedule of the user and coordinating care betweencaregivers associated with the user. In one exemplary embodiment, theprocess may be performed by an engagement and care support platform(“ECSP”) computer system (also referred to herein as an “ECSP platform”and an “ECSP server”). In another embodiment, the process may beperformed by a digital care circle platform, which may be configured toperform steps that are substantially similar to those described hereinfor the ECSP computer system.

As described below, the systems and methods described herein mayleverage different types of data (e.g., user and caregiver data, userevents including tasks, activities, and appointments, caregiverschedules, smart device data, and mobile device data) to facilitateindependent engagement of a user (e.g., a senior user) and provideinformation associated with that information to a caregiver.

The caregivers associated with the user may include people who normallytake care of the user (e.g., family members, friends, paid caregivers,etc.) and service providers of the user (e.g., health careprofessionals, such as doctors, nurses, physical therapists,occupational therapists, etc.). The caregivers often have busyschedules, and it may be difficult for the caregivers to coordinatecaring for the user. Accordingly, friction between caregivers may arisefrom constantly trying to coordinate care and scheduling to take care ofthe user. Moreover, it can be unclear whether or when certain tasks havebeen completed, which may lead to redundancy in task completion and/orincomplete tasks.

In addition, some senior users may desire a level of independence fromtheir caregivers, and may only want or need assistance for certaintasks. Accordingly, the user may grow frustrated with unpredictablecaregiver schedules and/or unnecessary caregiver presence.

The systems and methods described herein ensure that the user isactively engaged in their care schedule and that each caregiver isinformed about the status of the user and their assigned tasks of thecare schedule. In addition, caregivers are able to care for the userand/or carry out tasks for the user and may reduce friction betweencaregivers by providing a platform that automatically assigns careduties to caregivers based upon information (e.g., scheduling andcalendar information) input by the caregivers and ensures that thecaregivers complete their assigned duties. Further, the systems andmethods described herein may learn about the user and associatedcaregivers and adjust interactions with the user and associatedcaregivers and the coordinating of the care schedule of the user as wellas engagement of the user based upon the learning. Moreover, the systemsand methods herein facilitate independent senior engagement with aninterface that enables caregivers to remotely view the user'sinteractions with the interface. Therefore, the caregivers can beassured of the senior user's state.

Exemplary User and Caregiver Data Collection

In the exemplary embodiment, an engagement and care support platform(e.g., provided by an engagement and care support platform server) mayleverage different kinds of data (e.g., user and caregiver data, userevents, caregiver schedules, sensor data, and mobile device data) tocoordinate a care schedule of a user between one or more caregiversassociated with the user and/or promote user engagement with theengagement and care support platform. In the exemplary embodiment, aprimary caregiver (e.g., an admin caregiver) may register for theengagement and care support platform (“ECSP”) service provided by anECSP server through an application (e.g., a ECSP application) on amobile device associated with the admin caregiver, or any other suitabledevice that may access the ECSP application and/or a website associatedwith the ECSP application. The user may also register for the ECSPapplication for himself or herself.

In registering for the ECSP service, the admin caregiver may provide theECSP server with information associated with the user. The informationassociated with the user may include user data (e.g., name, birthdate,height, weight, etc.), user tasks (e.g., taking medicine, bathing,eating, paying bills, getting groceries, car maintenance, homemaintenance, etc.), user activities (e.g., social activities, like bingoand golfing, physical activities, like working out and keeping active,etc.), user interests and hobbies (e.g., fishing, home improvement,gardening, etc.) user appointments (e.g., recurring appointments likeyearly physicals and bimonthly haircuts, etc.), user alert preferences(e.g., when and through which method users prefer to be alerted), andany other information associated with the user that may be useful to theECSP server. This information associated with the user may be stored ina “senior profile,” which may be leveraged to generate activityschedules, provide relevant content (e.g., articles or games), and thelike. In other embodiments, the user may register for the service andprovide the ECSP server with information for the senior profilethemselves. In some embodiments, the admin caregiver and/or the user mayprovide contact information for users that may not be caregivers, suchas non-caregiver family members, social groups (e.g., member of a bookclub), etc. The contact information for these users may be identifiedand stored using “shortcut” names or phrases that identify the group.For example, contact information for a user's three children may beidentified collectively as a “Kids” group.

Further, in registering for the ECSP service, the admin caregiver mayinvite other caregivers to be a part of a care team for the user and/orthe user may invite other caregivers himself or herself. For example,the admin caregiver may provide the ECSP server with a list of emailsand/or phone numbers of other caregivers who are associated with theuser. The ECSP server may send an invitation link and/or code to theother caregivers instructing the other caregivers on how to sign up forthe care team for the user associated with the admin caregiver.

Each caregiver, including the admin caregiver, may register themselvesfor the ECSP service. In registering for the ECSP service, thecaregivers may provide the ECSP server with caregiver information (e.g.,name, contact information, relationship to the user), caregiver scheduleinformation (e.g., known work and/or activity schedules of thecaregivers), caregiver alert preferences (e.g., when and through whichmethod caregivers prefer to be alerted), and/or any other caregiverinformation that may be useful to the ECSP server. In some embodiments,the caregivers may link their digital calendars (e.g., provided on amobile device associated with the caregiver) to the ECSP server suchthat the caregivers do not have to manually input scheduling dataavailable to the ECSP server into the digital calendar. The user and thecaregivers may update and/or edit the user and caregiver data at anytime (e.g., through the ECSP application). Further, the admin caregiverand/or the user may require that each registered caregiver be approvedbefore the caregivers are officially added to the caregivers of the userby the ECSP application. For example, the ECSP application may push anotification to the mobile device associated with the admin caregiverand/or a user device associated with the user each time a new caregiveris registered. The notification may prompt the admin caregiver and/orthe user to accept or deny (e.g., through a push notification or voicecommand) the new caregiver. If the new caregiver is accepted by the userand/or the admin caregiver, the new caregiver may be automatically addedto the caregivers associated with the user by the ECSP application.

In the exemplary embodiment, if the caregiver is a person who normallytakes care of the user and needs to view and/or be notified of theschedule of the user, the caregiver may fully register for the ECSPservice. If the caregiver is a person who only provides certain servicesto the user (e.g., a doctor, nurse, physical therapist, occupationaltherapist, etc.) and/or is socially involved with the user for specificactivities (e.g., a garden club member, a book club member, etc.), thecaregiver may have very limited access to the ECSP service, and the ECSPserver may have very limited access to the caregiver data (e.g., theECSP server may simply receive calendar updates from the caregiver if anevent related to the user is scheduled).

In the exemplary embodiment, the ECSP server may also be configured toreceive sensor data from sensors associated with the user and/or thecaregivers. For example, sensors may include smart home device sensors(e.g., AMAZON ALEXA, GOOGLE HOME, and/or RING doorbells), wearabledevice sensors (e.g., APPLE WATCH and FITBIT), smart device sensors(e.g., smart pillboxes), sensors associated with a mobile device of theuser and caregivers (e.g., GPS sensors), and any other sensors. In theexemplary embodiment, the ECSP server may be configured to store thereceived data (e.g., user data, caregiver data, sensor data, etc.) in amemory.

Exemplary Care Coordination

In the exemplary embodiment, the ECSP server may be configured toprocess all of the user and caregiver data (e.g., events of the user,and schedules and preferences of the caregivers) the EC SP serverreceives from the user and caregivers (e.g., through the ECSPapplication) and coordinate a care schedule of the user between thecaregivers and/or promote user engagement with the ECSP application. TheECSP server may automatically assign each task, activity, and/orappointment of the user to the caregivers based upon the receivedcaregiver data, and the received caregiver data may include caregiverpreferences and schedules. The ECSP server may also promote userengagement with the ECSP server by “learning” about the user from thereceived user data and suggest different types of media (e.g., articles,videos, movies, TV shows, etc.) that may interest the user. The ECSPserver may further suggest different activities based on the “learning”about the user. For example, the ECSP server may suggest and/or send alink to an online invite for a new gardening club if the user typicallyreads about gardening.

The ECSP server may allow caregivers to easily assign tasks, activities,and events of the user amongst themselves such that each caregiver isinformed about the care schedule of the user, including which caregiveris assigned to each task of the care schedule. For example, the primarycaregiver of the user may assign tasks that the primary caregiver knowseach caregiver can handle and/or the caregivers can assign tasks tothemselves as the tasks are created (e.g., through the ECSPapplication). The ECSP server may also process the caregiver dataassociated with the caregivers and compare the caregiver data to thetask, activity, and appointment schedule of the user. Based upon thecompared data, the ECSP server may assign each task, activity, andappointment of the user to each of the caregivers. For example, the ECSPserver may assign the events to the primary caregiver first (based upona schedule of the primary caregiver) and then assign the rest of theevents not assigned to the primary caregiver to other caregivers basedupon the schedules of the other caregivers.

Further, the user and/or caregivers may assign some events to the userto carry out when the user does not need assistance with the events(e.g., taking medication, doing nightly security checks, and/or doingdaily exercises). Once the events have been assigned to the user and/orthe caregivers, the ECSP server may create a care schedule of the user.The care schedule may include all of the user's events, and the userand/or caregiver assigned to the events. The care schedule may be storedin, for example, a care database, in a memory device associated with theECSP server.

The ECSP server may determine if events of the care schedule of the userare taken care of by the assigned caregiver through, for example, sensordata received by the ECSP server. For instance, if a user is scheduledto take medicine at a certain time two times a day, the ECSP server mayreceive data from a sensor (e.g., a smart pillbox) associated with theuser to determine if the pill box was opened at the certain scheduledtimes. Further, for example, if a caregiver is scheduled to take theuser to a doctor's appointment at a certain time, the ECSP server mayreceive location data of the user and the caregiver (e.g., from mobiledevices of the user and/or caregiver) to determine if the caregiver tookthe user to the doctor's appointment. Additionally, if the user isscheduled to receive a grocery delivery at a certain time, the EC SPserver may receive data (e.g., from a smart home device like a smartdoorbell) to determine if the groceries were delivered for the user(e.g., through determining if the doorbell was rung and/or a deliveryperson showed up around the scheduled time).

If the ECSP server determines that a task, activity, and/or appointmenthas not been carried out, the ECSP server may alert (e.g., through theECSP application) the user and/or caregivers based upon the user andcaregiver data (e.g., alert preferences). Further, the ECSP server maynotify the caregivers, based on the alert preferences of the caregivers,when a scheduled event has been carried out by the caregiver and/orothers (e.g., service providers). In other embodiments, the user andcaregivers may manually enter that the events of the user have beentaken care of by the caregiver.

Exemplary Care Coordination Support Application

In the exemplary embodiment, an ECSP application is associated with theECSP server. The ECSP application may be configured to receive user andcaregiver data, display the care schedule of the user to the caregivers,and/or alert and/or notify the user and caregivers of assigned events.The ECSP application may be run on a device associated with the userand/or caregiver (e.g., a mobile device and/or laptop of the user orcaregiver). The ECSP application may be configured to display the careschedule of the user based upon the preference of the user andcaregivers. For example, the ECSP application may display a list ofdaily, weekly, and/or monthly tasks assigned to the user and/orcaregivers, a calendar that marks when the user and/or caregiver hasassigned events, and any other display method that allows the user andcaregivers to easily see and interact with the care schedule of theuser.

In the exemplary embodiment, the ECSP server may include a chatbot thatis embedded in the ECSP application and has access to the informationstored by the ECSP server (e.g., scheduled/assigned events, user data,caregiver data, etc.). The chatbot may be any suitable chatbot and/orrobo-assist device that functions as described herein. The chatbot mayassist the user in interacting with the ECSP application (e.g., thechatbot may recognize voice commands and/or typed commands from theuser), the user and caregivers in adding, editing, and/or deleting userand caregiver data, coordinating care of the user between thecaregivers, receiving information about the assigned care schedule,and/or receiving information about how the user and caregivers arecarrying out the care schedule. For example, instead of a user having tophysically check-in with the ECSP application (e.g., through a userinterface of the device associated with the user) and/or the user and/orcaregiver having to manually input each event of the user, eachnotification request of the user and caregivers, and/or each scheduleitem of the caregivers, the user and caregivers may give instructions tothe chatbot (e.g., through typing and/or speaking commands and/orquestions using plain or colloquial language, rather than structuredcommands, into the chatbot through the ECSP application). For example,the chatbot may interpret the user and/or caregivers saying, “Go home,”“Go to my dashboard,” “Go to my home screen,” or “Return home” all ascommands to navigate to a dashboard of the ECSP application.Additionally, “Show me my care circle,” “View my care circle,” “Who's inmy care circle,” and “Show people in my care circle” may be interpretedby the chatbot as commands to view the care circle, “Help,” “Help me,”“Show me the customer support number,” and “Contact customer support”may be interpreted by the chatbot as commands to get help from customerservice associated with the ECSP application, “Approve,” “I want toapprove [name of caregiver],” “Allow,” and “Allow [name of caregiver] tojoin” may be interpreted by the chatbot as commands to approve newcaregivers, etc. Accordingly, the chatbot may be able to commands in theform of plain and colloquial language from the user and garegivers intoactions. Also, for example, if the user just added a daily medication totheir routine, the user may instruct the chatbot to add the medicationto the daily list of tasks for the user to carry out. Further, acaregiver may instruct the chatbot that the user's lawn needs to bemowed every week in the summer.

The ECSP application may be configured to passively assist incoordinating care for the user between the caregivers. For example, ifthe caregivers mostly have the care schedule of the user figured out andscheduled, the chatbot may be configured to monitor what the users andcaregivers input into the chatbot and provide assistance if necessary.For instance, if one caregiver inputs into the chatbot that thecaregiver is taking the user to an appointment on Monday at 2 p.m., thechatbot may respond to the caregiver that the appointment is on theircalendar. If another caregiver says that the caregiver is taking theuser to breakfast on Tuesday at 10 a.m., the chatbot may respond to thecaregiver that the event is not in their calendar and ask the caregiverif the caregiver would like the event added to their calendar. If thecaregiver responds that the caregiver would like the event added totheir calendar, the chatbot may cause the event to be added to thecalendar of the caregiver.

The user and caregivers may also ask the ECSP application questions(e.g., through the chatbot), and the ECSP application may, for example,convert the natural-language question of the user and caregivers into aquery, run the query against a database (e.g., an event database storedin a memory device), and transmit a response to the question to theprocessor including an answer to the question, in response to the queryreturning the at least one event. For example, the user may ask the ECSPapplication who is taking them to a haircut appointment or oil changeappointment, and the caregiver may ask the ECSP application to identifythe last time the user had a bath.

The ECSP application may also notify and/or send alerts to the user andcaregivers based upon the user and caregiver alert preferences. Forexample, the ECSP application may notify a caregiver that a user has notyet taken their medicine, and the ECSP application t may ask thecaregiver if the caregiver would like the ECSP application to send areminder to the user to take their medicine (e.g., through an audiblealert, such as via a chatbot). If the caregiver says yes, the ECSPapplication may automatically cause the reminder to be sent to the user.

In the exemplary embodiment, the ECSP application may further beconfigured to learn from the user and caregiver requests, responses,and/or questions. For example, if the ECSP application often notifies acaregiver that the user forgets to take a nightly dose of medication,and the caregiver typically tells the ECSP application to remind theuser to take their medication in response to the notification from theECSP application, the ECSP application may automatically cause the ECSPcomputing device to start reminding the user to take their nightlymedicine dosage without input from the caregiver.

Further, the ECSP application may be configured to verbally explainscheduled events, scheduling conflicts, and/or missed scheduled eventsthat may arise to the user and/or caregivers. For example, if the ECSPapplication determines that a scheduling conflict has arisen (e.g., thecaregiver and/or the user are double-booked), the ECSP application mayverbally engage with the user and/or caregiver to explain the schedulingconflict. In verbally engaging with the user and/or caregiver, the ECSPapplication may be configured to converse with the user and/or caregiverto resolve the scheduling conflict. Further, if the ECSP applicationdetermines that a scheduled event was missed, the ECSP application mayverbally alert the user and/or caregiver of the missed event. Inverbally alerting the user and/or caregiver, the ECSP application mayalso be configured to converse with the user and/or caregiver to resolveand/or reschedule the missed event.

In one exemplary embodiment, the ECSP server may be configured to usethe ECSP application to facilitate engagement from the user. Inparticular, the ECSP server may leverage the ECSP application toencourage interaction and “check-ins” by the user. For example, the ECSPapplication may provide a daily interactive user interface to the user,may prompt the user to check-in proactively (e.g., through providing aprompt that the user answers), and/or may determine that the user hasnot checked-in and respond in a reactive manner (e.g., by notifying oneor more caregivers that the user has not checked-in in a certain amountof days). As described herein, the daily interactive user interface mayinclude any scheduled activities the user has in their calendar. Inaddition, the daily interactive user interface may display pictures orcontent provided by one or more caregivers. For example, a caregiver mayprovide a picture or article for display within the daily interactiveuser interface. The ECSP application may further provide an interactionprompt to the user that encourages the user to interact therewith. Theinteraction prompt may be visual, such as encouraging the user to “tap”a picture or to access a content item (e.g., read an article). Theinteraction prompt may additionally or alternatively be an audio prompt.For example, the audio prompt may be a question posed to the user (e.g.,“How are you feeling today?”) or may be related to a past or futurescheduled activity (e.g., “Did you enjoy your Garden Club meetingyesterday?”, “Are you looking forward to seeing the kids for dinner?”).The interaction prompt may additionally or alternatively encourage theuser to perform an activity (e.g., “Why don't you take a five-minutewalk around?”) The ECSP server may leverage sensor data (e.g., from awearable device or camera) to determine whether the user completes thesuggested activity.

The ECSP server may then transmit messages to a caregiver that provideinformation about whether and how the user is responding to theinteraction prompts. For example, the ECSP server determines whether theuser responded to the interaction prompt and includes an indication ofany response in daily messages to the caregiver. In this way, thecaregiver may be assured that the user is in a positive physical and/ormental state. If the user does not respond to the interaction promptsfor a threshold number of days (e.g., two days), the ECSP server maytransmit an alert to the caregiver. The alert includes an indicationthat the user has not responded to interaction prompts for the thresholdnumber of days, which may indicate that the user is hurt, confused, orotherwise in need of a more personal check-in.

The ECSP server may further be configured to generate caregiveranalytics, and the ECSP application may be configured to display thegenerated analytics to the user and caregivers. The ECSP server maygenerate activity hour, effort hour, and task distribution analytics foreach caregiver and compare the analytics to the other caregivers. Forexample, the ECSP server may generate a chart of the time each caregiverspends caring for the user and/or the time each caregiver spends puttingin effort to the care of the user for a predetermined period of time.The ECSP server may further generate a chart of a percentage of tasksfor the user that each caregiver handles over the predetermined periodof time.

Exemplary Care Coordination Support System

FIG. 1 depicts a view of an exemplary engagement and care supportplatform (“ECSP”) system 100 that may be used in facilitation engagementof a user and coordinating care of the user between caregiversassociated with the user. ECSP system 100 may include a carecoordination support platform (“ECSP”) computing device 102. In theexemplary embodiment, ECSP computing device 102 is in communication withclient devices 104, a chatbot server 106, and third party servers 108.ECSP computing device 102 is also in communication with a database 118and may communicate with database 118 through a database server 116.

In some embodiments, database server 116 is a component of ECSPcomputing device 102. In other embodiments, database server 116 isseparate from ECSP computing device 102. In some embodiments, ECSPsystem 100 may include a plurality of ECSP computing devices 102, clientdevices 104, third party servers 108, and/or databases 118.

In the exemplary embodiment, ECSP computing device 102 may be configuredto store user and caregiver data, generate and/or store a care schedulefor the user, and facilitate user engagement with the care schedule(e.g., by prompting the user to check in daily with the caregivers,displaying the care schedule in a user-friendly way, allowing the userto interact with the care schedule, etc.). ECSP computing device 102 mayreceive user and caregiver data from client devices 104 and use the userand caregiver data to register users and caregivers and generate careschedules for the user and caregivers. For example, a user and acaregiver may download an ECSP application 110 to a device (e.g., clientdevice 104) and input data into ECSP application 110 for registrationwith a service provided by ECSP computing device 102. The user andcaregivers may also access a website of ECSP system 100 using a webbrowser, and input user data into the website to register with ECSPsystem 100.

The user data may include personal data (e.g., name, birthdate, height,weight, etc.), user tasks (e.g., taking medicine, bathing, eating,paying bills, getting groceries, car maintenance, home maintenance,etc.), user activities (e.g., social activities, like bingo and golfing,physical activities, like working out and keeping active, etc.), userappointments (e.g., recurring appointments like yearly physicals andbimonthly haircuts, etc.), and any other information associated with theuser that may be useful to ECSP computing device 102.

The caregiver data may include personal information (e.g., name, contactinformation, relationship to the user, role in caring for the user,etc.), caregiver schedule information (e.g., known work and/or activityschedules of the caregivers), caregiver preferences (e.g., which eventsthe caregiver prefers to assist the user with), and any otherinformation associated with the caregivers that may be useful to ECSPcomputing device 102.

ECSP application 110 may also receive other data from the user andcaregivers including notification preferences of the user and caregivers(e.g., preferences of when the user and caregivers would like to benotified and how the user and caregivers would like to be notified, suchas receiving a text notification and/or a push button notification fromECSP application 110).

In the exemplary embodiment, users and caregivers may update the userand caregiver data at any time through ECSP application 110. Forexample, user data that may need to be updated may include a change inand/or newly scheduled events of the user, and a change in a dailymedication schedule of the user. For example, caregiver data that mayneed to be updated may include a change in and/or a new availabilityschedule of the caregiver and a new activity scheduled by the caregiver.

ECSP application 110 may be in communication with other applications ofclient device 104 and may import user and caregiver data from the otherapplications. For example, caregivers may allow ECSP application 110 toretrieve data from a calendar application of the caregivers such thatthe caregivers may only need to update the schedule associated with thecaregiver in one application (e.g., a calendar application).

In the exemplary embodiment, ECSP computing device 102 may be configuredto process all of the user and caregiver data ECSP computing device 102receives from the user and caregivers (e.g., through ECSP application110) and coordinate a care schedule of the user between the caregiversand facilitate user engagement in the care schedule. In the exemplaryembodiment, the caregivers may manually assign tasks to themselvesand/or other caregivers through ECSP computing device 102, and ECSPcomputing device 102 may store the assigned tasks of the care schedulefor each caregiver. In some embodiments, ECSP computing device 102 mayautomatically assign each task, activity, and/or appointment of the userto the caregivers based upon the received caregiver data.

In the exemplary embodiment, client devices 104 may be computers thatinclude a web browser or a software application, which enables clientdevices 104 to access remote computer devices, such as ECSP computingdevice 102, using the Internet or other network. More specifically,client devices 104 may be communicatively coupled to the Internetthrough many interfaces including, but not limited to, at least one of anetwork, such as the Internet, a local area network (LAN), a wide areanetwork (WAN), or an integrated services digital network (ISDN), adial-up-connection, a digital subscriber line (DSL), a cellular phoneconnection, and a cable modem. Client devices 104 may be any devicecapable of accessing the Internet including, but not limited to, adesktop computer, a laptop computer, a personal digital assistant (PDA),a cellular phone, a smartphone, a tablet, a smart home device (e.g.,AMAZON ALEXA, AMAZON ECHO, GOOGLE HOME, and/or RING doorbells), aphablet, wearable electronics (e.g., LIFE ALERT and/or FITBIT), smartwatch (e.g., APPLE WATCH), or other web-based connectable equipment ormobile devices.

Further, ECSP computing device 102 may be communicatively coupled toclient devices 104 and may receive information from client devices 104.Client device 104 associated with the user may be different from clientdevice 104 associated with the caregiver. For example, client device 104associated with the user may be a smart home device (e.g., AMAZON ALEXA)because the user may prefer interacting with client device 104 throughaudio commands rather than physically interacting with client device104. Client device 104 associated with the caregiver may be asmartphone.

In the exemplary embodiment, some client devices 104 include ECSPapplication 110 and a user interface 112. User interface 112 may beused, for example, to receive notifications from ECSP computing device102 and/or to input and verify information to be sent to ECSP computingdevice 102. ECSP application 110 may be, for example, a program orapplication that runs on client device 104. Further, ECSP application110 associated with the user client device 104 may have differentfunctionality as ECSP application 110 associated with the caregiverclient devices 104, as is explained in further detail herein, especiallywith regard to the screenshots of the ECSP application 110.

ECSP computing device 102 may be configured to facilitate userengagement with the care schedule and the caregivers. For example, ECSPcomputing device 102 (e.g., through ECSP application 110) may displaythe daily care schedule of the user such that the user is made aware of,and can interact with, their care schedule. ECSP computing device 102may prompt the user to check-in with the caregivers through ECSPcomputing device 102. For example, ECSP computing device 102 may displaya “Check-In” box that the user may press so that the caregivers knowthat the user is doing okay and has interacted with their care schedule.For further example, ECSP computing device 102 may keep track of howoften the user interacts with ECSP computing device 102 instead of, orin addition to, the user manually checking in. Accordingly, thecaregivers are assured that the user is okay, and the user plays anactive part in their care schedule.

In some embodiments, ECSP computing device 102 may be configured todisplay (e.g., through ECSP application 110) the generated care scheduleto the user and/or caregivers. ECSP computing device 102 may display thegenerated care schedule to the user and caregivers through task lists,graphs, calendars, and any other suitable interface that allows the userand caregiver to easily take in and interact with the care schedule ofthe user.

ESCP computing device 102 may be in communication with chatbot server106 and leverage the chatbot functionality thereof to implement at leastsome of the functionality disclosed herein (e.g., to transmitinformation to and/or receive information from a user and/or one or morecaregivers).

Database server 116 may be communicatively coupled to database 118 thatstores data. In one embodiment, database 118 may include user data,caregiver data, device data, mobile device data, assignment data, andnotification data. In the exemplary embodiment, database 118 may bestored remotely from ECSP computing device 102. In some embodiments,database 118 may be decentralized. In the exemplary embodiment, a userand/or caregiver, may access database 118 via their respective clientdevices 104 by logging onto ECSP computing device 102, as describedherein.

Third party server 108 may be any third party server that ECSP computingdevice 102 is in communication with that provides additionalfunctionality of ECSP computing device 102 and/or ECSP application 110.For example, third party server 108 may be servers associated with thirdparties including online retailers/delivery services (e.g., AMAZON,grocery delivery services, food deliver services flower deliveryservicers, etc.), ride sharing services (e.g., UBER and LYFT), andhospital/doctor's offices servers. Because ECSP computing device 102 isin communication with third party server 108, the user and/or caregiversmay directly access third party servers 108 through ECSP application110. For example, if a caregiver wants to order flowers for the user,the caregiver may be able to order the flowers from a third partyservice (e.g., AMAZON) directly through ECSP computing device 102. Insome embodiments, third party server 108 may provide updates to the userand/or caregivers through the ECSP application 110 (e.g., notifying theuser that their ride is on their way and/or updating the caregiver onthe status of their delivery to the user).

Exemplary User Computer Device

FIG. 2 illustrates an exemplary configuration 200 of an exemplary usercomputing device 202. In some embodiments, user computing device 202 maybe in communication with a care coordination support platform computingdevice (such as ECSP computing device 102, shown in FIG. 1). Usercomputing device 202 may be representative of, but is not limited toclient devices 104 and/or sensor servers 108. For example, usercomputing device 202 may be a mobile device, smartphone, tablet,smartwatch, wearable electronic, laptop, desktop, or another type ofcomputing device associated with an account holder (e.g., the userand/or the associated caregivers).

User computer device 202 may be operated by a user 204 (e.g., a user ofECSP system 100, shown in FIG. 1 and substantially similar to the userand/or the caregivers described herein). User computer device 202 mayreceive input from user 204 via an input device 214. User computerdevice 202 includes a processor 208 for executing instructions. In someembodiments, executable instructions may be stored in a memory area 210.Processor 208 may include one or more processing units (e.g., in amulti-core configuration). Memory area 210 may be any device allowinginformation such as executable instructions and/or user and registrationdata to be stored and retrieved. Memory area 210 may include one or morecomputer-readable media.

User computer device 202 also may include at least one media outputcomponent 212 for presenting information to user 204. Media outputcomponent 212 may be any component capable of conveying information touser 204 and may be used to at least partially implement user interface112 (shown in FIG. 1). In some embodiments, media output component 212may include an output adapter (not shown), such as a video adapterand/or an audio adapter. An output adapter may be operatively coupled toprocessor 208 and operatively coupleable to an output device, such as adisplay device (e.g., a cathode ray tube (CRT), liquid crystal display(LCD), light emitting diode (LED) display, or “electronic ink” display)or an audio output device (e.g., a speaker or headphones).

In some embodiments, media output component 212 may be configured topresent a graphical user interface (e.g., a web browser and/or a clientapplication) to user 204. A graphical user interface may include, forexample, care calendars for the user and/or associated caregivers, listsof assigned tasks of the care schedule for the user and/or caregivers,notifications for the user and/or associated caregivers, assigned tasksof the caregivers, an activity analytics of the caregivers, and/or amessaging page for interacting with the user and/or caregivers. Thegraphical user interface may additionally include visual interactionprompts that are periodically (e.g., daily, twice daily, every otherday, etc.) provided to the user. Visual interaction prompts may includeinstructions, images, content (e.g., articles or other text), and thelike. Media output component 212 may additionally or alternativelyprovide audible interaction prompts (e.g., via an audio output device).

In some embodiments, user computer device 202 may include input device214 for receiving input from user 204. User 204 may use input device 214to, without limitation, interact with ECSP system 100 (e.g., using ECSPapplication 110), ECSP computing device 102, or any of client devices104 and third party servers 108 (shown in FIG. 1). Input device 214 mayinclude, for example, a keyboard, a pointing device, a mouse, a stylus,and/or a touch sensitive panel (e.g., a touch pad or a touch screen) andmay be used to at least partially implement user interface 112 (shown inFIG. 1). A single component, such as a touch screen, may function asboth an output device of media output component 212 and input device214. User computer device 202 may further include at least one sensor,including, for example, a gyroscope, an accelerometer, a positiondetector, a biometric input device, and/or an audio input device. Insome embodiments, at least some data collected by user computer device202 may be transmitted to ECSP computing device 102. In the exemplaryembodiment, data collected by user computer device 202 may be includedin user and caregiver data.

User computer device 202 may also include a communication interface 216,communicatively coupled to any of ECSP computing device 102, clientdevices 104, and third party servers 108. Communication interface 216may include, for example, a wired or wireless network adapter and/or awireless data transceiver for use with a mobile telecommunicationsnetwork.

Stored in memory area 210 may be, for example, computer-readableinstructions for providing a user interface to user 204 via media outputcomponent 212 and, optionally, receiving and processing input from inputdevice 214. The user interface may include, among other possibilities, aweb browser and/or a client application. Web browsers enable users, suchas user 204, to display and interact with media and other informationtypically embedded on a web page, a website, or an application hosted byECSP computing device 102 and/or client device 104. A client applicationmay allow user 204 to interact with, for example, any of ECSP computingdevice 102, client devices 104, and third party servers 108. Forexample, instructions may be stored by a cloud service and the output ofthe execution of the instructions sent to the media output component212. User computing device 200 may include additional, less, oralternate functionality, including that discussed elsewhere herein.

Exemplary Server Device

FIG. 3 depicts an exemplary configuration 300 of an exemplary servercomputer device 302, in accordance with one embodiment of the presentdisclosure. Server computer device 302 may include, but is not limitedto, ECSP computing device 102 (shown in FIG. 1). Server computer device302 may include a processor 305 for executing instructions. Instructionsmay be stored in a memory area 310. Processor 305 may include one ormore processing units (e.g., in a multi-core configuration).

Processor 305 may be operatively coupled to a communication interface315 such that server computer device 302 may be capable of communicatingwith a remote device such as another server computer device 302 or auser computing device, such as client device 104 (shown in FIG. 1). Forexample, communication interface 315 may receive requests from ortransmit requests to client devices 104 via the Internet.

Processor 305 may also be operatively coupled to a storage device 325.Storage device 325 may be any computer-operated hardware suitable forstoring and/or retrieving data, such as, but not limited to, dataassociated with database 118 (shown in FIG. 1). In some embodiments,storage device 325 may be integrated in server computer device 302. Forexample, server computer device 302 may include one or more hard diskdrives as storage device 325. In other embodiments, storage device 325may be external to server computer device 302 and may be accessed by aplurality of server computer devices 302. For example, storage device325 may include a storage area network (SAN), a network attached storage(NAS) system, and/or multiple storage units such as hard disks and/orsolid state disks in a redundant array of inexpensive disks (RAID)configuration.

In some embodiments, processor 305 may be operatively coupled to storagedevice 325 via a storage interface 320. Storage interface 320 may be anycomponent capable of providing processor 305 with access to storagedevice 325. Storage interface 320 may include, for example, an AdvancedTechnology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, aSmall Computer System Interface (SCSI) adapter, a RAID controller, a SANadapter, a network adapter, and/or any component providing processor 305with access to storage device 320.

Processor 305 executes computer-executable instructions for implementingaspects of the disclosure. In some embodiments, processor 305 may betransformed into a special purpose microprocessor by executingcomputer-executable instructions or by otherwise being programmed.

Exemplary Computer-Implemented Method

FIG. 4 depicts a flow chart illustrating a computer-implemented method400 for facilitating engagement of a senior user. In the exemplaryembodiment, method 400 may be implemented by a care coordination supportplatform computer system such as ECSP computing device 102 (shown inFIG. 1).

Method 400 may include registering 402 a user and registering 404 atleast one caregiver associated with the user for a care coordinationsupport platform service (e.g., provided by ECSP computer system shownin FIG. 1). Method 400 may also include generating 406 a senior profilebased upon user personal and scheduling data provided during registering402. Method 400 may further include building 408 a daily interactiveuser interface that reflects the senior profile.

Method 400 may also include displaying 410 the daily interactive userinterface at a first client device associated with the user, forexample, via an application associated with ECSP computing device 102,shown in FIG. 1. Method 400 may further include causing 412 the firstclient device to initiate a daily interaction prompt to the user, anddetermining 414 whether any user interaction was received at the firstclient device in response to the daily interaction prompt. In addition,method 400 may include transmitting 416 a daily update message to asecond client device associated with the caregiver, the daily updatemessage including an indication of whether any user interaction wasreceived at the first client device.

Exemplary Computer Device

FIG. 5 depicts a diagram 500 of components of one or more exemplarycomputing devices 510 that may be used in care coordination supportplatform system 100 (shown in FIG. 1). In some embodiments, computingdevice 510 may be similar to ECSP computing device 102 (shown in FIG.1). Database 520 may be coupled with several separate components withincomputing device 510, which perform specific tasks. In this embodiment,database 520 may include user data 521, caregiver data 522, sensor data523, calendar data 524, task data 525, assignment data 526, andnotification data 527. In some embodiments, database 520 is similar todatabase 118 (shown in FIG. 1).

Computing device 510 may include database 520, as well as data storagedevices 530. Computing device 510 may also include an analyticscomponent 540 for analyzing received user data to generate a seniorprofile based upon the received data. The senior profile may be used torecommend activities, provide content of interest (e.g., articles),track schedules, and the like. Analytics component 540 may be furtherconfigured to analyze received data to determine whether a user hasresponded to an interaction prompt, as described herein. Computingdevice 510 may further include application/display component 550 forgenerating and displaying information (e.g., interaction prompts) tousers, such as through ECSP application 110 (shown in FIG. 1), andsupporting ECSP application 110. Moreover, computing device 510 mayinclude communications component 560 for receiving and transmitting data(e.g., to and from client devices 104), such as user data 521, caregiverdata 522, sensor data 523, calendar data 524, task data 525, assignmentdata 526, and notification data (e.g., daily update messages) 527, aswell as responses to interaction prompts. Computing devices 510 mayinclude additional, less, or alternate functionality, including thatdiscussed elsewhere herein.

Exemplary Care Coordination Support Application

FIGS. 6-18 include screenshots of one example embodiment of anapplication (e.g., ECSP application 110, shown in FIG. 1) executable aspart of an engagement and care support platform system (e.g., engagementand care support platform system 100, shown in FIG. 1). The applicationmay be accessible on any suitable electronic device, such as a mobilephone, tablet, smart home device, watch, or any other computing device.The application enables a user to check in and interact with theapplication, determine what tasks caregivers need to complete, view acare schedule of the user, and enables one or more caregivers to addtasks for the user, view the tasks that the one or more caregivers haveto complete for and/or with the user, and coordinate the care schedulebetween the one or more caregivers.

In some embodiments, the application may enable the user and the one ormore caregivers to subscribe to alerts, notifications, and/or reminders.

The application may be configured to communicate with various othersoftware and/or applications on the computing devices of the usersand/or the one or more caregivers. For example, the application may beable to access or otherwise communicate with calendar applicationsand/or contact applications. The application may be configured toretrieve data from and/or report data to these other applications. Inaddition, the application may be configured to track, monitor, and/orrecord application utilization metrics for the user and/or thecaregivers, such as how often the user and/or the caregivers access theapplication, and the various features of the application used by theuser and/or the caregivers.

In one embodiment, the application, once downloaded onto the computingdevice of the user and/or the caregivers, may not require internetconnectivity to perform some or all of the functionality of theapplication (e.g., setting alerts and notifying the user and/orcaregivers of the alerts). In some embodiments, all or a portion of thedata input by the user and/or caregivers into the application(including, for example, application utilization metrics, task logs,etc.) may be electronically transmitted to a server (e.g., ECSP server102) for processing, and the processed data may be transmitted back forfurther processing and/or display by the application.

In the exemplary embodiment, the application can be configured to, interalia, allow the user to quickly and easily check-in with the caregivers,giving the caregivers peace of mind, proactively allowing the user tocheck-in (e.g., by prompting the user to answer a question like “How areyou feeling today?”), providing a reactive response if/when the userdoes not check in (e.g., by notifying one or more of the caregivers),providing an interactive display for the user and the caregivers,provide tools for the user and the caregivers to coordinate key tasksassociated with the care schedule of the user, providing smartsuggestions of media for the user to increase user engagement with theapplication, allowing caregivers to easily share photos and videos withthe user, allowing the user to easily view the shared photos and videos,allowing the user to view their care schedule with audio commands and/orthrough interacting with the digital display of the application, andproviding social features that help the user and caregivers stay andfeel connected.

FIG. 6 illustrates an initial welcome page 600 that may include a header602. Although not specifically shown, header 602 may include a homebutton, a back button, and any other buttons to help the user and/or thecaregivers navigate the application. In some embodiments, initialwelcome page 600 may further include a footer (not specifically shown)that may include additional buttons to help the user and/or thecaregiver navigate the application. Initial welcome screen 600 may alsoinclude a “Register a New Care Team” button 604 that, when clicked, maycause the application to display a user registration screen 700.

FIG. 7 illustrates user registration page 700 for the application. Userregistration page 700 may include a first field 702 for the user and/oran administrative caregiver (e.g., “admin caregiver”) to enter the nameof the user and a second field 704 to, if user registration page 700 isfilled out by the admin caregiver, enter the relationship of the admincaregiver to the user.

Further, user registration page 700 may include a third field 708 forthe user and/or admin caregiver to enter email addresses, phone numbers,and/or other contact information of other caregivers such that theapplication may invite the other caregivers to download the application.User registration page 700 may include a button 710 that, when clicked,may cause the application to open a contacts list of the user such thatthe user can choose contacts to invite instead of manually filling outthird field 708.

User registration page may include an “Invite” button 712, that, whenclicked, may cause the application to invite the other caregivers todownload the application and/or show a caregiver registration page 800,a “Save” button 714 that, when clicked, may cause the application tosave the information in fields 702, 704, and 708, and a “Cancel” button716 that, when clicked, may cause the application to go back to initialwelcome page 600. Once other caregivers download the application, theother caregivers may be directly navigated to caregiver registrationpage 800 and may bypass initial welcome page 600 and/or userregistration page 700.

FIG. 8 illustrates caregiver registration page 800 for the applicationthat allows the admin caregiver and/or the other caregivers to registerfor the application. Caregiver registration page 800 may include a firstfield 802 for the caregiver to enter the name of the caregiver, a secondfield 804 for the caregiver to enter a password for the application, athird field 806 for the caregiver to enter a group that the caregiverbelongs to (e.g., “Kids,” “Grandkids,” etc.), a fourth field 808 for thecaregiver to enter a relationship of the caregiver to the user, and afifth field 810 for the caregiver to enter contact information (e.g.,phone number(s), email address, and/or home address).

Caregiver registration page 800 may further include a “Register” button812 that, when clicked, may cause the application to save and store theinformation that caregiver entered into fields 802, 804, 806, 808,and/or 810, and display a welcome screen 900, and caregiver registrationpage 800 may include a “Cancel” button 814 that, when clicked, may causethe application to close and show a different screen (e.g., a homescreen) of the device running the application.

FIG. 9 illustrates welcome page 900 that may be the first page that theuser and/or the admin caregiver are directed to until a user care teamis complete (e.g., the user and all caregivers associated with the userare registered through the application). Welcome page 900 may include a“View User Care Team” button 902 that, when pressed, may cause theapplication to display a user care team page 1000. Welcome page 900 mayfurther include a “Sync User Device” button 904 (e.g., if the device ofthe user has not been synced with the application) that, when pressed,may cause the application to display instructions for syncing the userdevice with the application (not specifically shown).

FIG. 10 illustrates user care team page 1000 that may allow the userand/or the admin caregiver to view and/or edit the care team associatedwith the user. User care team page 1000 may include a list 1002 ofregistered members of the care team including the names of thecaregivers (e.g., entered by the caregivers in first field 802 ofcaregiver registration page 800, shown in FIG. 8) and groups of thecaregivers (e.g., entered by the caregivers in third field 806 ofcaregiver registration page 800, shown in FIG. 8).

User care team page 1000 may also include an “Edit” button 1006 that,when clicked, allows the user and/or admin caregiver to edit list 1002and a “Done” button 1004 that, when clicked, causes the application tosave the care team and store the care team as fully registered. Usercare team page 1000 may also include a first field 1008 where the userand/or the admin caregiver may manually enter contact information ofadditional caregivers to add to the care team.

Additionally or alternatively, the user and/or the admin caregiver maypress a “Open Contacts” button 1010 that, when pressed, causes theapplication to open the contacts of the user and/or admin caregiver andallow the user and/or admin caregiver to automatically choose whichcontacts the user and/or admin caregiver would like to invite to thecare team. When the user and/or admin caregiver is done adding contactinformation of additional caregivers, the user and/or admin caregivermay press an “Invite” button 1012 that, when clicked, causes theapplication to invite the additional caregivers to register for theapplication.

FIG. 11A shows an example user home page 1100 displayed on a deviceassociated with the user that the user may be directed to when thedevice is synced with the application. User home page 1100 may include awelcome greeting 1102 and a list 1104 of daily tasks scheduled for theuser. User home page 1100 may further include a “View Calendar” button1106 that, when pressed, may cause the application to display a detailedcalendar of the user (not specifically shown). User home page 1100 mayfurther include a “Check In” button that, when pressed, may notify thecaregivers (e.g., in message 1202 and 1302 of user home screen 1200 and1300, shown in FIGS. 12 and 13, respectively) that the user has checkedin. User home page 1100 may also include media 1112 shared with the userby the caregivers and a “View All Photos” button 1110 that, whenpressed, causes the application to display all media 1112 shared withthe user.

FIG. 11B shows an alternative user home page 1115 displayed on a deviceassociated with the user that the user may be directed to when thedevice is synced with the application. User home page 1115 may include a“Check In” button 1116 that, when pressed, functions substantially thesame as button 1108 of FIG. 11A. That is, button 1116, when pressed, maynotify the caregivers (e.g., in message 1202 and 1232 of user homescreen 1200 and 1230, shown in FIGS. 12A and 12B, respectively) that theuser has checked in. Home page 1115 may further include a “Calendar”button 1117 that, when pressed, may cause the application to display ascreen showing the calendar of the user (e.g., displayed as a dailycalendar, a weekly calendar, a monthly calendar, etc.). Home page 1115may further include a “Lists” button 1118 that, when pressed, may causethe application to display a screen showing lists associated with theuser (e.g., a grocery list, a to-do list, etc.). User home page 1115 mayalso include a “Photos” button 1119 that, when pressed, may cause theapplication to display photos shared with the user.

FIGS. 11C-11L show user interaction pages 1120, 1130, 1140, 1150, 1155,1160, 1165, 1170, 1180, and 1190. User interaction pages 1120 and 1130are displayed on the application when the user interacts with theapplication. For example, user interaction page 1120 displays that theuser used voice-activation to command the application to “Add mow thelawn to my to-do list.” User interaction page 1130 displays that theapplication received the command from the user as shown in userinteraction page 1120 and added the command to the to-do list of theuser. User interaction page 1140 displays that the user used a command(e.g., either a voice command or pressed button 1118 of user interactionscreen 1115) to add “yellow mustard” to their “Grocery list.” Userinteraction page 1140 includes a “Yes” button 1142 that, when pressed,causes the application to add yellow mustard to the Grocery list anddisplay user interaction page 1150, and a “No” button 1144 that, whenpressed, causes the application to not add yellow mustard to the Grocerylist and return to, for example, user home page 1110 or alternative userhome page 1115. User interaction page 1150 includes a prompt for theuser about whether the user will handle the newly added Grocery listitem or if the user would like somebody else (e.g., a caregiver) tohandle the newly added Grocery list item. User interaction page 1150includes a “Me” button 1152 that, when pressed, causes the applicationto add the newly added Grocery list item to the lists of the user andthen display, for example, user home page 1110 or alternative home page1115, and a “Somebody else” button 1154 that, when pressed, causes theapplication to add the newly added Grocery list item to the lists of oneof the caregivers of the user. Accordingly, the “Somebody else” button1154, when pressed, may cause the application to display a list of thecaregivers associated with the user (not shown) such that the user canpick the caregiver to assign the task to.

User interaction pages 1155, 1160, 1165, 1170, and 1180 are displayed onthe application when the application actively interacts with the userfor a check in. For example, user interaction page 1140 displays thatthe application has prompted the user to check-in via an audio prompt(e.g., asking the user “How are you this morning?”). User interactionpage 1160 displays that the user used a voice command to respond to theapplication that the user is feeling fine (e.g., by saying, “I feelfine. No stiffness in my knees.”).

User interaction page 1165 displays that the application received theresponse of the user and includes a prompt for the user to decidewhether to share the check-in with the caregivers (e.g., the applicationasks the user, “Would you like to share this check-in with your carecircle?”). User interaction page 1170 displays that the applicationreceived the response of the user to the prompt of user interaction page1165 (e.g., the user responded that the user would like to share theircheck-in with their care circle and the application displays that thecheck-in has been shared). User interaction page 1180 displays analternate way for the user to check-in. Specifically, user interactionpage 1180 displays a message 1182 from a caregiver asking the user tocheck in with the caregiver soon. Further, user interaction page 1180includes three check-in buttons, a first check-in button 1184, a secondcheck-in button 1186, and a third check-in button 1188. The firstcheck-in button 1184, when pressed or commanded to be pressed (e.g., viavoice command), causes the application to send a message to thecaregiver associated with the message 1182 that the user is doing welltoday. The second check-in button 1186, when pressed or commanded to bepressed (e.g., via voice command), causes the application to send amessage to the caregiver associated with the message 1182 that the useris not doing well today. The third check-in button 1188, when pressed orcommanded to be pressed (e.g., via voice command), causes theapplication to send a message to the caregiver associated with themessage 1182 that the user feels loved today. Accordingly, when any offirst, second, and third check-in buttons 1184, 1186, and 1188 ispressed or commanded to be pressed, the application counts the user aschecked-in for the day.

User interaction page 1190 displays that a caregiver has been added tothe Care Circle and prompts the user to accept or deny the user. Userinteraction page 1190 includes a “Yes” button 1192 and a “No” button1194. The “Yes” button 1192, when pressed or commanded to be pressed(e.g., through voice command), causes the application to add therespective caregiver to be added to the Care Circle of the user. The“No” button 1194, when pressed or commanded to be pressed (e.g., throughvoice command), causes the application to deny the respective caregiveraccess to the Care Circle of the user. Accordingly, the applicationallows the user to control the members of the Care Circle of caregiversassociated with the user.

FIGS. 12A and 12B are examples of caregiver home screens 1200 and 1230.For example, caregiver home screens 1200 and 1230 may be the firstscreen that is displayed when the caregivers log-in to the applicationafter registering the care team has been completed (e.g., in user careteam page 1000). Caregiver home screens 1200 and 1230 may besubstantially similar and may include a list 1206 of activitiesscheduled for the user and times 1208 associated with the activities.Caregiver home screens 1200 and 1230 may further include a notification1210 of what the user needs help with (e.g., unassigned tasks) and abutton 1212 that, when pressed, cause the application to assign the taskof notification 1210 to the caregiver.

Caregiver home screens 1200 and 1230 may further include navigationbuttons 1214, 1216, 1218, 1220, and 1222 that, when pressed, cause theapplication to display different screens of the application. Forexample, pressing button 1214 may cause the application to display oneof caregiver home screens 1200 and 1230. Caregiver home screens 1200 and1230 may further include a message 1202 and 1232, respectively, that maybe accompanied by a logo 1204 and 1234. For example, when message 1202and/or 1232 indicates that the user has checked-in for a specific day,logo 1204 and/or 1234 may be filled in (e.g., as shown in logo 1204).When message 1202 and/or 1232 indicates that the user has not checked-infor a specific day, logo 1204 and/or 1234 may not be filled in (e.g., asshown in logo 1234).

FIGS. 13A and 13B are alternative examples of caregiver home screens1300 and 1350. For example, caregiver home screens 1300 and 1350 may bethe first screen that is displayed when the caregivers log-in to theapplication after registering the care team has been completed (e.g., inuser care team page 1000). Caregiver home screens 1300 and 1350 mayinclude an action button 1304 that, when pressed, may cause theapplication to display a screen related to the action button (e.g., agrocery list view screen). Caregiver home screens 1300 and 1350 mayfurther include an upcoming events list 1306 that display upcomingevents scheduled for and/or associated with the user (e.g., a doctor'sappointment scheduled at 10:30 A.M.).

Caregiver home screens 1300 and 1350 may be substantially similar andmay include a user activity message 1302 and 1352. User activitymessages 1302 and/or 1352 may display the most recent user activityand/or interaction with the application. For example, user activitymessages 1302 and/or 1352 may show that the user viewed a grocery list(e.g., as shown in user activity message 1302) and/or that the useradded to the grocery list and list the items that the user added (e.g.,as shown in user activity message 1352).

FIG. 14 shows a caregiver feed page 1400 (e.g., which the applicationdisplays when button 1216 of FIGS. 12 and 13 is pressed). Caregiver feedpage 1400 may include a header 1402, a field 1404 accompanied by a videobutton 1406, a photo button 1408, and a check-in button 1410, and acaregiver activity list 1412. The caregiver may give updates and includeany information that the caregiver wishes to share with the othercaregivers in field 1404. Video button 1406, when pressed, allows thecaregiver to share a video on the application, photo button 1408, whenpressed, allows the caregiver to share a photo (or multiple photos) onthe application, and check-in button 1410, when pressed, allows thecaregiver to check-in with the other caregivers (e.g., when thecaregiver is carrying out an assigned task for the user and/or checkingin on the user). Caregiver activity list 1412 shows a feed of recentcaregiver activities (e.g., assigned tasks, adding appointments, sharingphotos and/or videos, etc.).

FIG. 15 shows a caregiver schedule page 1500 (e.g., which theapplication displays when button 1218 of FIGS. 12 and 13 is pressed)that allows the caregivers to add events and/or appointments to the carecalendar of the user. Caregiver schedule page 1500 may include a header1502, fields 1504, and pull-down bars 1506. The caregivers may provideinformation about the new event in field 1504, and the caregivers mayuse pull-down bars 1506 to assign the event to a specific caregiver.

FIGS. 16 and 17 show caregiver list pages 1600 and 1700. Caregiver listpage 1600 (e.g., which the application may display when button 1220 ofFIGS. 12 and 13 is pressed) may include a header 1602, differentcategories of lists 1604, and list items 1606 that are assigned to thecaregiver. List items 1606 may be accompanied by check circles 1608 thatthe caregivers may check when they have completed corresponding listitem 1606 assigned to the caregivers. Caregiver list page 1700 may bedisplayed by the application when any of categories of lists 1604 ispressed. Caregiver list page 1700 may include list items 1702 that fitinto the chosen category, and list items 1702 may be accompanied bycheck circles 1704 that the caregivers may check when they (or when theyknow other caregivers have) completed corresponding list item 1702. Listitems 1702 may further be accompanied by pictures 1706, and pictures1706 may show the caregiver assigned to each of list items 1702.

FIG. 18 shows a care circle page 1800 (e.g., which the application maydisplay when button 1222 of FIGS. 12A and 12B is pressed). Care circlepage 1800 may include a header 1802, an image 1804, groupings 1806 ofevents, interests 1808, caregiver profiles 1810, and shared photos 1812.Image 1804 may display an image of the user and/or of any of thecaregivers. Groupings 1806 may show an overview of the number and typesof events that the user has scheduled in the care calendar. Interests1808 may allow the caregivers to choose certain interests 1808 of theuser such that the application can better prepare a user profile.Caregiver profiles 1810 may show a brief profile of each of thecaregivers of the care circle. Shared photos 1812 may show all photosshared by the caregivers of the care circle.

In other embodiments, the application may include additional featuresand functionality. For example, the application may present a userinterface to the user and/or caregivers including an option for the userand/or caregivers to view or input additional data to their profile. Theapplication may additionally provide an option for the user and/orcaregivers to input, view, and/or edit medication information for theuser. For example, the user and/or caregivers may be able to see theuser's daily medication schedule and determine if the user is taking themedication (e.g., through a sensor, as described above).

Machine Learning & Other Matters

The computer systems and computer-implemented methods discussed hereinmay include additional, less, or alternate actions and/orfunctionalities, including those discussed elsewhere herein. Thecomputer systems may include or be implemented via computer-executableinstructions stored on non-transitory computer-readable media. Themethods may be implemented via one or more local or remote processors,transceivers, servers, and/or sensors (such as processors, transceivers,servers, and/or sensors mounted on mobile computing devices, orassociated with smart infrastructure or remote servers), and/or viacomputer executable instructions stored on non-transitorycomputer-readable media or medium.

In some embodiments, a care coordination support platform computingdevice is configured to implement machine learning, such that the carecoordination support platform computing device “learns” to analyze,organize, and/or process data without being explicitly programmed.Machine learning may be implemented through machine learning methods andalgorithms (“ML methods and algorithms”). In an exemplary embodiment, amachine learning module (“ML module”) is configured to implement MLmethods and algorithms. In some embodiments, ML methods and algorithmsare applied to data inputs and generate machine learning outputs (“MLoutputs”). Data inputs may include but are not limited to: user data,caregiver data, sensor data, assignment data, calendar data, task data,and/or alert data. ML outputs may include but are not limited to: userdata, caregiver data, calendar data, task data, and/or assignment data.In some embodiments, data inputs may include certain ML outputs.

In some embodiments, at least one of a plurality of ML methods andalgorithms may be applied, which may include but are not limited to:linear or logistic regression, instance-based algorithms, regularizationalgorithms, decision trees, Bayesian networks, cluster analysis,association rule learning, artificial neural networks, deep learning,combined learning, reinforced learning, dimensionality reduction, andsupport vector machines. In various embodiments, the implemented MLmethods and algorithms are directed toward at least one of a pluralityof categorizations of machine learning, such as supervised learning,unsupervised learning, and reinforcement learning.

In one embodiment, the ML module employs supervised learning, whichinvolves identifying patterns in existing data to make predictions aboutsubsequently received data. Specifically, the ML module is “trained”using training data, which includes example inputs and associatedexample outputs. Based upon the training data, the ML module maygenerate a predictive function which maps outputs to inputs and mayutilize the predictive function to generate ML outputs based upon datainputs. The example inputs and example outputs of the training data mayinclude any of the data inputs or ML outputs described above. Forexample, a ML module may receive training data comprising user data,caregiver data, and assignment data associated with the user data andcaregiver data. The ML module may then generate a model which mapsassignment data to aspects of user data and caregiver data. The MLmodule may then generate assignment data as a ML output based uponsubsequently received user data and caregiver data.

In another embodiment, a ML module may employ unsupervised learning,which involves finding meaningful relationships in unorganized data.Unlike supervised learning, unsupervised learning does not involveuser-initiated training based upon example inputs with associatedoutputs. Rather, in unsupervised learning, the ML module may organizeunlabeled data according to a relationship determined by at least one MLmethod/algorithm employed by the ML module. Unorganized data may includeany combination of data inputs and/or ML outputs as described above. Forexample, a ML module may receive unlabeled data comprising user data,caregiver data, and calendar data. The ML module may employ anunsupervised learning method such as “clustering” to identify patternsand organize the unlabeled data into meaningful groups. The newlyorganized data may be used, for example, to generate a model whichassociates user data and caregiver data to calendar data.

In yet another embodiment, a ML module may employ reinforcementlearning, which involves optimizing outputs based upon feedback from areward signal. Specifically, the ML module may receive a user-definedreward signal definition, receive a data input, utilize adecision-making model to generate a ML output based upon the data input,receive a reward signal based upon the reward signal definition and theML output, and alter the decision-making model so as to receive astronger reward signal for subsequently generated ML outputs. Othertypes of machine learning may also be employed, including deep orcombined learning techniques.

The reward signal definition may be based upon any of the data inputs orML outputs described above. For example, a ML module may implementreinforcement learning in generating assignment data for caregivers. TheML module may utilize a decision-making model to generate assignmentdata for caregivers based upon task data, and may further receiveuser-satisfaction data indicating a level of satisfaction experienced bya user and a caregiver who engaged in a transaction (e.g., the caregivercarrying out a task for the user). A reward signal may be generated bycomparing the user-satisfaction data to an assignment score between theuser and the caregiver.

Based upon the reward signal, the ML module may update thedecision-making model such that subsequently generated assignment scoresmore accurately predict user satisfaction. For example, the ML modulemay determine that a specific caregiver has taken the user to fourdoctor's appointments. The user may enjoy the caregiver taking the userto the doctor's appointments, and the caregiver may enjoy taking theuser to the doctor's appointments because the doctor's appointments maybe close to the caregiver's house. Therefore, the user and the caregivermay both rate the “transaction” highly. Accordingly, the ML module maylearn to automatically assign doctor's appointments to the specificcaregiver.

Exemplary Virtual Care Circle Functionality

In one aspect, a digital solution is provided that will allow seniorsstay independent longer in their homes, and that will use technology tocreate a connected care environment and platform. With the presentembodiments, a new digital platform will provide a senior's care circlean easy way to stay connected and help coordinate care virtually. Thedigital platform may include a new application and chatbot for seniors,and new mobile applications for caregivers/family members/friends toelectronically communication, and may be part of a subscription service.

The new, innovative digital platform and application/chatbot may improvethe quality of life and care for seniors, and help give their familymembers added peace of mind, as well as provide unique voice solutionsthat help seniors' ability to communicate with their care circle fromtheir homes.

In one aspect, the senior will have a voice and touch interface poweredby the digital platform and/or caregiver circle application that canhelp them feel more connected and supported by their care circle, whiledelivering a personalized experience to them. The digital platform mayconnect to the care circle mobile app running on mobile device of thecare circle members that provides updates and information throughout theday. The care circle can share information back to the senior—creating avirtual circle of support and two-way communication at any time of theday. In one embodiment, the digital platform may include or utilizeAmazon's Echo Show™, or similar technologies.

Some of the features utilized by this digital solution include: (1)quick check-in to reassure care circle members; (2) interactivedashboard with scrolling list of daily activities; (3) tools tocoordinate key tasks across the care circle; (4) smart-suggestions forevents, content, and activities; (5) music and photos sent or deliveredto the senior's computing device and/or application; (6) the ability toview the senior's full calendar with audio commands and visual displayon their application; (7) social features to help everyone stayconnected and up-to-date; and/or other features mentioned elsewhereherein.

The solutions discussed herein will be useful in helping manage care ofa loved one, and help family members coordinate care with their agingloved one using a caregiver circle application. The application,chatbot, mobile applications, and digital platform will assist withactivities of daily living, transportation, communication, and socialconnectivity that will be key in helping seniors' ability to “age inplace.”

A. Launching the Service

The care circle application, such as for use on mobile devices ofcaregivers and family members, may facilitate onboarding, setup, and/orprofile creation. A family member or a senior may order a product, suchas the Echo Show™ product, and download a mobile application to theirmobile device. The family member may create a caregiver profile forthemselves using the mobile application. Their profile may include theirname and a profile photo, and other information and preferences.

The family member may create, using the mobile application, an accountfor the senior, such as their father or mother, that connects with thefamily member's profile and/or account. The family member may providedetails about, and/or preferences of, the senior using the mobileapplication, such as the senior's name and a profile photo for thesenior. The senior's profile may include other information, such assenior preferences for activities, events, movies, content, tv shows,music, restaurants, service providers, grocery stores, means oftransportation, etc.

A sibling of the family member, for example, may also want to be part ofthe senior's care circle, and the family member may select an “AddMember” icon of the mobile application to add their sibling to thesenior's care circle. The family member may also add, via the mobileapplication, details about their sibling, such as their name and emailaddress, and other information. The family member may add additionalcaregivers/family members/friends to the senior's care circle using themobile application.

The mobile application and platform may then send electronic invitationsto the mobile devices or email addresses of the members of the carecircle added by the originating family member. The electronicinvitations may include a link to a mobile application for download thatwill allow the members of the care circle and/or senior toelectronically communicate via the mobile application and digitalplatform.

The senior may launch or open the application on their computing deviceand/or on an Alexa-based or other chatbot-based product. After which,the senior may be greeted with a personalized dashboard on their mobiledevice, tablet, or laptop (or other computing device). The dashboard mayinclude photos of family members, an icon or access to digital photos,an icon or access to a digital or virtual calendar or schedule ofevents, a “Check In” icon, today's date, and today's scheduled events(such as morning routine, or doctor's appointment). Once the senioropens or launches the application, all connected caregivers ordesignated caregivers that are part of the senior's care circle mayreceive an electronic notification that the senior opened theapplication via the mobile application running on their mobile devices.After which, as the senior provides updates (e.g., went to doctor, needgroceries, etc.) on his/her activities/events and well-being via theapplication on their device and/or via the chatbot, allcaregivers/family members in the senior's care circle may view thesenior's updates on their respective mobile applications and mobiledevices.

B. Managing the Virtual Care Circle

The care circle application may facilitate virtual care circlemanagement and user invitation. If the senior has friends or neighborsthat the senior wants to be able to participate in the senior's carecircle, the senior may add the friend or neighbor to their virtual carecircle via their application, mobile device or other computing device,and/or via the chatbot. Additionally or alternatively, one or morefamily members may add the friend or neighbor to the virtual care circlefor the senior via their mobile care circle application and/or mobiledevice.

The senior and/or the one or more family members may add the friend's orneighbor's contact information, such as electronic email or textaddress, and other details, and then select the type of electronicnotifications and communications that should be shared with the friendor neighbor via the senior's application or chatbot, or the mobileapplication running on a family member's mobile device, respectively.For instance, the senior and/or family members may want the friend orneighbor to know when help is needed for driving, scheduling, orordering things, such as groceries or other items, for the senior.

After accepting an electronic invitation to join the senior's carecircle, the friend or neighbor may download the mobile application ontotheir mobile device. The friend or neighbor may then be able to navigatea care circle feed that may consist of digital posts from all of themembers in the care circle, as well as from the senior.

For instance, from the care circle feed, the friend or neighbor may beable to see on the mobile application that the original family memberhas assigned various items or tasks (such as items or task from avirtual to-do list) to the friend or neighbor (e.g., pick up groceries).After those items or tasks have been completed, the friend or neighbormay virtually check them off via the mobile application so that thefamily member and/or other members of the virtual care circle see thatthose items have been completed via the mobile application running ontheir mobile devices. The friend or neighbor may also virtually post anupdate using the mobile application to make sure everyone in the virtualcare circle notices that he or she has completed the items assigned viathe mobile application running on their respective mobile devices.

The friend and neighbor may also virtually post text updates about thewell-being or health of the senior, and/or other events, via the mobileapplication. The family member or other members may comment or otherwiserespond to the updates via the mobile application and/or their mobiledevices.

C. Starting the Day Off Right

The virtual caregiver circle application may facilitate both “proactive”check-ins and “reactive” check-ins. For proactive check-ins, the seniormay open the senior living application on their device or using Alexa(or other chatbot), prompting an automatic check-in. Alexa or anotherchatbot may greet the senior and ask how they are feeling, such as “GoodMorning, Elmer. How are you doing this morning?” After which, the seniormay respond verbally, and their verbal response may be converted to atext response or message by the application and/or chatbot—such as “Ifeel fine, no stiffness in my knees.”

After which, the senior may be prompted by the chatbot and/orapplication to share his check-in with all caregivers, who can then viewthe senior's virtual post on the care circle feed. For instance, Alexaor another chatbot may ask “Would you like to share this check-in withyour care circle?” If the senior decides to share his check-in with allcaregivers/family members/friends, or one or more specific individuals,the chatbot or application may post the senior's update to the carecircle feed, and then the chatbot may verbally respond to the senior:“Okay, your message has been shared.”

The family members and other members of the care circle, may thenreceive an electronic notification via the mobile application on theirmobile devices that the senior has checked-in for the day. After thesenior checks-in, the senior may then view their digital dashboard ontheir computing device, and/or ask the chatbot what activities/eventshave scheduled for the day. The dashboard may then display a visual ofthe senior's scheduled activities for the day, and/or the chatbot mayverbally detail the activities for the senior, such as “Call Addison at10:30 am,” or detail the activity by type, time, and location (“Doctor'sappointment, St. Joseph Hospital, at 1 pm”).

For reactive check-ins, such as when the senior fails to activelycheck-in with the application and/or chatbot on their own, one or morefamily members or other members of the care circle may receive anelectronic notification that the senior has not checked-in this morningnor interacted with the application and/or chatbot. After which, afamily member or member of the virtual care circle may decide to givethe senior a video or telephone call, using the mobile application. Thesenior may respond to video or telephone call using the application ontheir computing device or chatbot. For instance, the chatbot may ask thesenior if the senior is alright, and the senior may respond—either byconversing with the chatbot or by using their application on theircomputing device—that the senior was having coffee with a friend thismorning, thus providing peace of mind to the family member that thesenior is doing fine.

D. Everyone Knows What's Going on

The caregiver circle application may facilitate collaborative schedulingand calendars. For instance, one or more family members/care circlemembers may be sent reminders about various activities or events of thesenior, depending on settings. For instance, a primary family member inthe virtual care circle may be sent reminders about doctor appointmentsfor the senior in the morning of the appointment, and a notification ofwhich member in care circle is responsible for ensuring the senior hastransportation to the appointment. After the appointment, the member ofthe care circle responsible for the appointment may virtually post amessage providing an update on how the appointment went to the carecircle feed and provide digital access to the message to one or moremembers of the virtual care circle.

For instance, a daughter may virtually post “Dad's post-surgery resultslook great, range of motion is better than expected” via the mobileapplication on her mobile device. Other members of the virtual carecircle may receive electronic notification of the daughter's update viawireless communication or data transmission and via the mobileapplication running on their respective mobile devices. For example, thedaughter's brother may receive, via his mobile care circle application,an electronic notification that his sister virtually posted anelectronic update on the status of their father, such as “Susan postedan update about Dad's Doctor's appointment this morning.” After which,the brother and other members of the virtual care circle may view thedaughter's update on the status of the senior (“Dad”) via the mobileapplication running on their respective mobile devices.

Then, continuing with this example, the daughter may create a virtualfollow-up event, such as a follow-up doctor's appointment as a follow-upevent, via her mobile application to add to the senior's virtualcalendar viewable by one or more of the members of the virtual carecircle. After which, one or more members in the virtual care circle mayreceive, depending upon individual permissions, an electronicnotification of the seniors' next medical appointment (e.g., “Susancreated a Follow-up Doctor's Appointment event”), and/or view thesenior's updated virtual calendar that includes the next medicalappointment.

Continuing with this example, the daughter may then designate whomreceives electronic notifications of the next medical appointment;assign responsibility for the next medical appointment to one or moremembers of the virtual care circle; and/or schedule transportation forthe senior to the next medical appointment via the mobile applicationrunning on her mobile device. After which, the senior may review and/orapprove of the scheduled medical appointment, proposed responsible caregiver, and/or proposed mode of transportation via their chatbot and/orapplication.

Additionally or alternatively, after the daughter posts the follow-updoctor's appointment event via her mobile application, a sibling maypost a virtual update regarding the event using his mobile applicationand mobile device. For instance, brother Jake may virtually post “Goingto drive Dad to his next appointment. Also, going to send him flowers!”via his mobile application. After Jake purchases the flowers through anonline service or provider, such as Amazon, Jake may update the carecircle feed and create a virtual event, via his mobile application, toalert the senior, his father in this example, of the delivery time, suchas via the senior's chatbot and/or application.

Additionally or alternatively in this example, the service providerremote server may also have certain access to the mobile applicationsand/or the senior's chatbot and/or application. For instance, theservice provider may provide a verbal or audible notice to the senior ofa type of delivery and time of delivery via the senior's chatbot and/orapplication. Further, the mobile applications may provide real-time ornear real-time video or images of the products being delivered to thesenior—in this example, video or images of flowers being delivered tothe senior.

E. Getting Things Done

The caregiver circle application may facilitate collaborative lists. Forexample, the senior may notice that his/her lawn needs to be mowed. Tohis/her virtual to-do list, the senior may add “Orderlandscaping/lawnmowing” via the seniors' chatbot and/or application. Forinstance, the senior may say “Alexa, open State Farm,” and then “Add mowthe lawn to my to-do list.”

The senior's chatbot and/or application may then add mowing the lawn tothe senior's virtual to-do list. For example, the senior's chatbot mayrespond: “Done. ‘Mow the lawn’ has been added to your to-do list.”

After which, family members and/or care circle members may receive anelectronic notification that the senior has updated their virtual to-dolist. For instance, virtual care circle members may receive, via theirrespective mobile applications, an electronic message that indicatesthat the senior has updated their virtual to-do list—such as electronicnotification saying “Elmer added an item to his to-do list. Let's helphim complete some tasks.”

After which, one or more designated family members and/or care circlemembers may take or assign responsibility for the item via a “To-do”icon on their respective mobile application, and/or the senior may alsoassign responsibility for the task via the senior's chatbot and/orapplication. For example, a primary family member responsible forassigning tasks to various members of the virtual care circle may assignthe task to herself/himself, or the senior may assign the task to one ofthe care circle members via the senior's chatbot.

Then the senior, and/or assigning family member and/or care circlemember, may view the listed items and also view who has been assignedand/or accepted responsibility for each virtual to-do item, such as viathe senior's chatbot and/or application and/or via the virtual carecircle members' mobile application, respectively. As examples, thevirtual to-do items may include “Mow the lawn”; “Walk the dog”; “Getmail”; “Schedule an appointment”; “Schedule a gutter cleaningappointment”; “Coordinate a ride's to Dad's doctor's appointment”; “Pickup Dad's medicine at pharmacy”; “Help Dad prepare and file his taxes”;“Find cleaning service for Dad's house”; and/or other to-do itemspresented via a display or via the voice of a chatbot. The virtual to-doitems may include other items, including those mentioned elsewhereherein.

A family member/care circle member may review the senior's virtualcalendar via their mobile application, or a machine learning module,model, algorithm, or program may be programmed, to find a time toschedule a virtual to-do item for the senior. Additionally oralternatively, the senior may assign a virtual to-do item to one or morefamily members/care circle members via the senior's chatbot and/orapplication. For instance, a primary family member that has access tothe senior's virtual calendar may decide upon a lawn service provider,and schedule a time and date to mow the senior's lawn using the mobileapplication running on their mobile device. The lawn service providermay be selected via the internet, such as selected via Amazon.com.Additionally or alternatively, the lawn service provider's websiteand/or Amazon.com may also be programmed with functionality tocommunicate or otherwise interact with the senior via the senior'schatbot to schedule a time for the lawn service provider to mow thesenior's lawn.

Once the to-do item is assigned, electronic reminders may generated forthe senior. For instance, voice-based reminders may be generated via thesenior's chatbot. Text or visual-based reminders may be generated anddisplayed via the senior's application. Voice-based and text orvisual-based reminders may also be sent to the mobile applications ofone or more family members/care circle members. For instance, on the dayof the lawn service, the daughter may be electronically notified via hermobile application when the lawn service will arrive and/or has arrived.Once the to-do items has been completed, the senior's virtual calendarmay be updated to such that all virtual care members can see that theitems has been completed via their mobile applications.

Exemplary Virtual Care Circle Platform & Functionality

FIG. 19 illustrates an exemplary computer-implemented method 1900 ofproviding a care circle platform that includes chatbot and mobileapplication functionality that facilitates coordination of virtual carecircle member communication and tasks. The computer-implemented method1900 may be implemented via one or more processors, transceivers,servers, sensors, applications, mobile applications, chatbots, andrelated technologies. In some embodiments, method 1900 may be carriedout by a digital care circle platform. The digital care circle platformmay be substantially similar to, and work in substantially the same wayas ECSP server 102 (shown in FIG. 1), described above.

The computer-implemented method 1900 may include, via one or moreprocessors and/or associated transceivers, using 1902 a digital carecircle platform to create user profiles and preferences of a senior andmultiple family members/caregivers with their permission or affirmativeconsent. The digital care circle platform may include chatbotfunctionality, and application and mobile application electroniccommunication functionality, such as that functionality discussedelsewhere herein, that permits electronic communication via computingdevices and/or mobile devices over one or more radio frequency links viawireless communication or data transmission. For instance, the seniormay use a chatbot and/or application to enter personal information tocreate their user profile and/or preferences. Members of the care circlemay use a mobile application running on their respective mobile devicesto enter personal information to create their respective user profiles.

The computer-implemented method 1900 may include, via one or moreprocessors and/or associated transceivers, creating 1904 a virtualcalendar of events and activities for the senior via the chatbot and/orapplication. The virtual calendar may include an interactive dashboardwith a scrolling list of daily activities and events for the senior. Theapplication may include the ability for the senior to view the fullcalendar after the senior enters one or more audible commands. Themethod 1900 may include launching the service, which may includeactivating the chatbot and application of the senior, as well as themobile applications of the virtual care circle members, once the seniorlogs into or launches the application for the first time.

The computer-implemented method 1900 may include, via one or moreprocessors and/or associated transceivers, allowing 1906 the seniorand/or family members/designated members of the virtual care circle tomanage the care circle via the senior's chatbot and/or application, orvia the family members'/designated care circle member's mobileapplication, respectively. The method 1900 may include generatingvirtual tools that facilitate coordinating key tasks across the virtualcare circle, such as assigning specific activities or events to be theresponsibility of specific individuals within the virtual care circle.

The computer-implemented method 1900 may include, via one or moreprocessors and/or associated transceivers, initiating 1908 “start theday off right” functionality. For instance, “proactive check-ins” may begenerated and/or initiated via the senior interacting with their chatbotand/or application on their computing device. As an example, everymorning the senior may check in with their chatbot and/or application ata given time to review their schedule, as well as provide an update totheir care circle as to how they are feeling.

The computer-implemented method may also include generating “reactivecheck-ins” for the senior to respond to via the senior's chatbot and/orapplication. For instance, if the senior doesn't check in by 8 a.m., thechatbot and/or application may ask the senior if they are doing alright,and the senior may respond to, or converse with, the chatbot verbally orrespond via the application textually or by touch.

Additionally or alternatively, a virtual care circle member may send avideo, text or voice message to the senior that the senior receives viatheir chatbot and/or application. The senior may respond to the virtualcare circle member's message via the chatbot and/or application. Forinstance, a virtual care circle member may send a text message “How areyou doing today Dad?” via their mobile application. The senior'sapplication may convert that text message to voice, and the senior'schatbot may verbally ask the senior: “How are you doing today Dad?” Atwhich point, the senior may verbally respond to the chatbot “I amfeeling well today. How are you?” After which, the conversation betweenthe senior and the virtual care circle member may continue with thesenior interacting with the chatbot to relay messages with the carecircle member's mobile application.

The computer-implemented method 1900 may include, via one or moreprocessors and/or associated transceivers, facilitating 1910 electronicand verbal communication and updates among the senior and the familymembers/care circle members regarding the senior's health/well-being andactivities via the senior's chatbot and application, and the mobileapplication of the respective family members/care circle members. Forinstance, a virtual “care circle feed” may include updates posted by thesenior using their chatbot or the application on their computing device,and/or updates posted by family member's/care circle member's via themobile application running on their respective mobile devices. Theupdates may be related to the senior's health, well-being, events,activities, location, etc. The updates may include photos and/or textmessages to create timeline of the senior's activities.

The computer-implemented method 1900 may include, via one or moreprocessors and/or associated transceivers, generating, creating, and/orproviding 1912 collaborative lists and/or collaborative scheduling toensure necessary tasks and items are accomplished for the senior. Forinstance, the method may include allowing the senior to virtually posttasks or events that he/she needs help with completing using theirchatbot and/or application. Care circle members may also virtually posttasks that need to be completed via their mobile applications. Carecircle members may virtually volunteer for, or accept responsibilityfor, various task via their mobile application. The senior may virtuallyaccept which volunteer care circle member to handle each task, or assignvarious tasks to specific individuals, via the senior's chatbot and/orapplication.

The computer-implemented method 1900 may include, via one or moreprocessors and/or associated transceivers, providing 1914smart-suggestions or recommendations for events, content, and/oractivities to the senior via the senior's chatbot and/or application.For instance, based upon “likes” or preferences in the senior's profile,the senior's chatbot and/or application may recommend various events oractivities to attend, and/or various online content to view, listen to,or read.

The computer-implemented method 1900 may include, via one or moreprocessors and/or associated transceivers, allowing 1916 the senior toaccess and view music and photos sent or received from familymembers'/care circle members' mobile applications via wirelesscommunication or data transmission over one or more radio frequencylinks. For instance, family members and/or care circle members may pushor send photos, music, and/or content to the senior that the senior canreview, view, or listen to on the senior's application. The virtual carecircle members may also push or send music that the senior can listen tovia the senior's chatbot or other digital platform. Thecomputer-implemented method may include additional, less, or alternatefunctionality, including that discussed elsewhere herein.

Exemplary Virtual Care Circle Embodiments

In one aspect, a digital care circle platform for electroniccommunication (i) within a virtual care circle, and (ii) between asenior's chatbot and application, and a mobile application running onmultiple care circle members' respective mobile devices may be provided.The digital care circle platform may include one or more processors,servers, sensors, wearables, and/or transceivers configured for wirelesscommunication and/or data transmission over one or more radio frequencylinks between and/or among the senior's chatbot and application, and themobile application running on each virtual care circle member's mobiledevice. The digital care circle platform may include, or beinterconnected with on communication with, (i) a chatbot associated withthe senior configured to receive one or more audible or verbal commandsfrom the senior; (ii) an application associated with a computing deviceof the senior, the application electronically interacting with and/orcommunicating with the chatbot; and/or (iii) a mobile applicationrunning on each virtual care circle member's mobile device andassociated with virtual care circle members, the mobile applicationconfigured to electronically communicate with the senior's chatbot andapplication running on the senior's computing device, such as viawireless communication or data transmission over one or more radiofrequency links.

The digital care circle platform may be configured to accept “event”posts from the senior via the chatbot and application, and from eachvirtual care circle member via the mobile device running on theirrespective mobile devices. The digital care circle platform may beconfigured to detect pro-active check-ins that are automaticallydetected and/or generated by the senior verbally or audibly interactingwith the chatbot and/or the senior accessing, viewing, or otherwiseinteracting with the application running on the senior's computingdevice. Once a pro-active check-in is detected, the digital care circleplatform may be configured to generate an electronic communicationdetailing the pro-active check-in as a “pro-active check-in event,” and(i) automatically virtually post the pro-active check-in event to a carecircle feed access via the mobile application running on one or morevirtual care circle member mobile devices, or (ii) otherwise transmitthe electronic communication to the mobile application running on one ormore virtual care circle member mobile devices to facilitate providingcommunication on the senior's current activity to the members of thevirtual care circle and quick check-in functionality. The digital carecircle platform may include additional, less, or alternatefunctionality, including that discussed elsewhere herein.

For instance, the digital care circle platform may be configured to, viaone or more processors, sensors, servers, wearables, and/ortransceivers: (a) actively monitor use of, and/or interaction with, thechatbot, application, and/or computing device by the senior; (b) detectthat the senior has not used or interacted with the chatbot,application, and/or computing device for a predetermined amount of time;and (c) if so, automatically generate an electronic message to thesenior, and transmit or send the electronic message to the chatbot,application, and/or computing device of the senior to facilitate quickcheck-ins and/or determining whether the senior needs assistance.Additionally or alternatively, the digital care circle platform may beconfigured to, via one or more processors, sensors, servers, wearables,and/or transceivers: when it is detected that the senior has not used orinteracted with the chatbot, application, and/or computing device for apredetermined amount of time, automatically generate an electronicnotification detailing such, and transmitting or otherwise sending theelectronic notification to one or more virtual care circle member mobiledevices to facilitate quick check-ins.

The digital care circle platform may be being configured to, via one ormore processors, sensors, servers, wearables, and/or transceivers: (a)actively monitor use of, and/or interaction with, the chatbot,application, and/or computing device by the senior; (b) detect that thesenior has not used or interacted with the chatbot, application, and/orcomputing device for a predetermined amount of time; (c) when it isdetected that the senior has not used or interacted with the chatbot,application, and/or computing device for a predetermined amount of time,automatically generate an electronic notification detailing such, andtransmitting or otherwise sending the electronic notification to one ormore virtual care circle member mobile devices; and/or (d) open, access,or create an audible or verbal communication channel between thesenior's chatbot and a virtual care circle member mobile device tofacilitate a real-time conversation between the senior and the virtualcare circle member, and/or quick check-ins.

The digital care circle platform may be configured to, via one or moreprocessors, sensors, servers, wearables, and/or transceivers: scan theinternet for preferred content (music, videos, articles, events,activities, etc.) for the senior based the senior's preferencesidentified or detailed in a virtual profile associated with the senior;and/or push preferred content, or otherwise providing links thereto, tothe senior's chatbot and/or the application running on the senior'scomputing device.

The digital care circle platform may be configured to, via one or moreprocessors, sensors, servers, wearables, and/or transceivers: (a)generate a virtual calendar of scheduled events and/or activities forthe senior, the virtual calendar including a scrolling list of scheduledevents and/or activities; and/or (b) display the virtual calendar ofscheduled events and/or activities for the senior via the application ona display screen of the senior's computing device, and/or audibly orverbally detail the calendar of scheduled events and/or activities forthe senior via the chatbot.

The digital care circle platform may be configured to, via one or moreprocessors, sensors, servers, wearables, and/or transceivers: (i)receive or accept audible or verbal commends from the senior via thechatbot regarding details of an event or activity to add to theirvirtual calendar; and/or (ii) add the event or activity to the senior'svirtual calendar.

The digital care circle platform may be configured to, via one or moreprocessors, sensors, servers, wearables, and/or transceivers: (a)receive or accept audible or verbal commends from the senior via thechatbot regarding details of a task or item to add to their virtualto-do list; (b) add the task or item to the senior's virtual to-do list;and/or (c) generate and post an electronic notification detailing thetask or item to the care circle feed accessible via the mobileapplication running on one or more virtual care circle member mobiledevices to facilitate coordinating key tasks among the members of thevirtual care circle.

The digital care circle platform may be configured to, via one or moreprocessors, sensors, servers, wearables, and/or transceivers: (a)receive or accept audible or verbal commands from the senior via thechatbot regarding identification of a virtual care circle member toassign the task or item to, or responsibility for; and/or (b) generateand post an electronic notification detailing which virtual care circlemember has been assigned the task or item to the care circle feedaccessible via the mobile application running on one or more virtualcare circle member mobile devices.

The digital care circle platform may be configured to, via one or moreprocessors, sensors, servers, wearables, and/or transceivers: (i)receive or accept user input from a virtual care circle member via themobile application regarding details of a task or item to add to thesenior's virtual to-do list; (ii) add the task or item to the senior'svirtual to-do list; and/or (iii) generate and post an electronicnotification detailing the task or item to the care circle feedaccessible via the mobile application running on one or more virtualcare circle member mobile devices to facilitate coordinating key tasksamong the members of the virtual care circle.

The digital care circle platform may be configured to, via one or moreprocessors, sensors, servers, wearables, and/or transceivers: (i)receive user input from a virtual care circle member via the mobileapplication regarding identification of a virtual care circle member toassign the task or item to, or responsibility for; and/or (ii) generateand post an electronic notification detailing which virtual care circlemember has been assigned the task or item to the care circle feedaccessible via the mobile application running on one or more virtualcare circle member mobile devices. The digital care circle platform mayalso be configured to, via one or more processors, sensors, servers,and/or transceivers: allow virtual care circle members to take or assignresponsibility for various tasks or items in a virtual to-do listassociated with the senior to facilitate collaborative scheduling andcoordinating key tasks across the virtual care circle.

In another aspect, a computer-implemented method for electroniccommunication (i) within a virtual care circle, and (ii) between asenior's chatbot and application, and a mobile application running onmultiple care circle members' respective mobile devices, the method mayinclude, via one or more processors, servers, sensors, wearables,digital platforms, and/or transceivers configured for wirelesscommunication and/or data transmission over one or more radio frequencylinks between and/or among the senior's chatbot and application, and themobile application running on each virtual care circle member's mobiledevice: (1) receiving one or more one or more audible or verbal commandsfrom the senior via the chatbot; (2) electronically interacting withand/or communicating with the chatbot via an application associated witha computing device of the senior; (3) electronically communicating withthe senior's chatbot and application running on the senior's computingdevice via a mobile application running on each virtual care circlemember's mobile device and associated with virtual care circle members,such as via wireless communication or data transmission over one or moreradio frequency links; (4) electronically accepting or wirelesslyreceiving event posts from the senior via the chatbot and application,and from each virtual care circle member via the mobile device runningon their respective mobile devices, such as via wireless communicationor data transmission over one or more radio frequency links; (5)detecting pro-active check-ins that are automatically detected and/orgenerated by the senior verbally or audibly interacting with the chatbotand/or the senior accessing, viewing, or otherwise interacting with theapplication running on the senior's computing device; and/or (6) once apro-active check-in is detected, generating an electronic communicationdetailing the pro-active check-in as a pro-active check-in event, and(a) automatically virtually posting the pro-active check-in event to acare circle feed access via the mobile application running on one ormore virtual care circle member mobile devices, and/or (b) otherwisetransmitting the electronic communication to the mobile applicationrunning on one or more virtual care circle member mobile devices tofacilitate providing communication on the senior's current activity tothe members of the virtual care circle and quick check-in functionality.The method may include additional, less, or alternate functionality,including that discussed elsewhere herein.

For instance, the computer-implemented method may include, via one ormore processors, sensors, servers, wearables, and/or transceivers:actively monitoring use of, and/or interaction with, the chatbot,application, and/or computing device by the senior; detecting that thesenior has not used or interacted with the chatbot, application, and/orcomputing device for a predetermined amount of time; and if so,automatically generating an electronic message to the senior, andtransmitting or sending the electronic message to the chatbot,application, and/or computing device of the senior to facilitate quickcheck-ins and/or determining whether the senior needs assistance. Themethod may also include, via one or more processors, sensors, servers,wearables, and/or transceivers: when it is detected that the senior hasnot used or interacted with the chatbot, application, and/or computingdevice for a predetermined amount of time (such as 12 hours, 18 hours,24 hours, 48 hours, etc.), automatically generating an electronicnotification detailing such, and transmitting or otherwise sending theelectronic notification to one or more virtual care circle member mobiledevices to facilitate quick check-ins.

The computer-implemented method may include, via one or more processors,sensors, servers, wearables, and/or transceivers: actively monitoringuse of, and/or interaction with, the chatbot, application, and/orcomputing device by the senior; detecting that the senior has not usedor interacted with the chatbot, application, and/or computing device fora predetermined amount of time; when it is detected that the senior hasnot used or interacted with the chatbot, application, and/or computingdevice for a predetermined amount of time (e.g., 24 hours, 48 hours,etc.), automatically generating an electronic notification detailingsuch, and transmitting or otherwise sending the electronic notificationto one or more virtual care circle member mobile devices; and/oropening, accessing, or creating an audible or verbal communicationchannel between the senior's chatbot and a virtual care circle membermobile device to facilitate a real-time conversation between the seniorand the virtual care circle member, and/or quick check-ins.

The computer-implemented method may include, via one or more processors,sensors, servers, wearables, and/or transceivers: scanning or searchingthe internet for preferred content (music, videos, articles, events,activities, etc.) for the senior based the senior's preferencesidentified or detailed in a virtual profile associated with the senior;and/or pushing preferred content, or otherwise providing links thereto,to the senior's chatbot and/or the application running on the senior'scomputing device.

The computer-implemented method may include, via one or more processors,sensors, servers, wearables, and/or transceivers: generating a virtualcalendar of scheduled events and/or activities for the senior, thevirtual calendar including a scrolling list of scheduled events and/oractivities; and displaying the virtual calendar of scheduled eventsand/or activities for the senior via the application on a display screenof the senior's computing device, and/or audibly or verbally detailingthe calendar of scheduled events and/or activities for the senior viathe chatbot.

The computer-implemented method may include, via one or more processors,sensors, servers, wearables, and/or transceivers: receiving audible orverbal commends from the senior via the chatbot regarding details of anevent or activity to add to their virtual calendar; and/or adding theevent or activity to the senior's virtual calendar.

The computer-implemented method may include, via one or more processors,sensors, servers, wearables, and/or transceivers: receiving or acceptingaudible or verbal commends from the senior via the chatbot regardingdetails of a task or item to add to their virtual to-do list; adding thetask or item to the senior's virtual to-do list; and/or generating andposting an electronic notification detailing the task or item to thecare circle feed accessible via the mobile application running on one ormore virtual care circle member mobile devices to facilitatecoordinating key tasks among the members of the virtual care circle. Themethod may include, via one or more processors, sensors, servers,wearables, and/or transceivers: receiving or accepting audible or verbalcommands from the senior via the chatbot regarding identification of avirtual care circle member to assign the task or item to, orresponsibility for; and/or generating and posting an electronicnotification detailing which virtual care circle member has beenassigned the task or item to the care circle feed accessible via themobile application running on one or more virtual care circle membermobile devices.

The computer-implemented method may include, via one or more processors,sensors, servers, wearables, and/or transceivers: receiving or acceptinguser input from a virtual care circle member via the mobile applicationregarding details of a task or item to add to the senior's virtual to-dolist; adding the task or item to the senior's virtual to-do list; and/orgenerating and posting an electronic notification detailing the task oritem to the care circle feed accessible via the mobile applicationrunning on one or more virtual care circle member mobile devices tofacilitate coordinating key tasks among the members of the virtual carecircle. The method may include, via one or more processors, sensors,servers, wearables, and/or transceivers: receiving or accepting userinput from a virtual care circle member via the mobile applicationregarding identification of a virtual care circle member to assign thetask or item to, or responsibility for; and/or generating and posting anelectronic notification detailing which virtual care circle member hasbeen assigned the task or item to the care circle feed accessible viathe mobile application running on one or more virtual care circle membermobile devices.

The method may also include, via one or more processors, sensors,servers, wearables, and/or transceivers: allowing virtual care circlemembers to take or assign responsibility for various tasks or items in avirtual to-do list associated with the senior to facilitatecollaborative scheduling and coordinating key tasks across the virtualcare circle.

Additional Considerations

With the foregoing, users and caregivers may opt-in or register to acare coordination support platform program or other type of program.After the users and caregivers give their affirmative consent orpermission, a care coordination support platform remote server maycollect data from the mobile devices, user computing devices, smart homecontrollers, smart vehicles, autonomous or semi-autonomous vehicles,smart infrastructure, smart buildings, smart aerial devices (e.g.,drones), and/or other smart devices, such as with the permission oraffirmative consent of the users and caregivers. The data collected maybe related to user activities and/or user/caregiver schedules andcurrent locations.

As will be appreciated based upon the foregoing specification, theabove-described embodiments of the disclosure may be implemented usingcomputer programming or engineering techniques including computersoftware, firmware, hardware or any combination or subset thereof. Anysuch resulting program, having computer-readable code means, may beembodied or provided within one or more computer-readable media, therebymaking a computer program product, i.e., an article of manufacture,according to the discussed embodiments of the disclosure. Thecomputer-readable media may be, for example, but is not limited to, afixed (hard) drive, diskette, optical disk, magnetic tape, semiconductormemory such as read-only memory (ROM), and/or any transmitting/receivingmedium such as the Internet or other communication network or link. Thearticle of manufacture containing the computer code may be made and/orused by executing the code directly from one medium, by copying the codefrom one medium to another medium, or by transmitting the code over anetwork.

These computer programs (also known as programs, software, softwareapplications, “apps”, or code) include machine instructions for aprogrammable processor, and can be implemented in a high-levelprocedural and/or object-oriented programming language, and/or inassembly/machine language. As used herein, the terms “machine-readablemedium” “computer-readable medium” refers to any computer programproduct, apparatus and/or device (e.g., magnetic discs, optical disks,memory, Programmable Logic Devices (PLDs)) used to provide machineinstructions and/or data to a programmable processor, including amachine-readable medium that receives machine instructions as amachine-readable signal. The “machine-readable medium” and“computer-readable medium,” however, do not include transitory signals.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

As used herein, a processor may include any programmable systemincluding systems using micro-controllers, reduced instruction setcircuits (RISC), application specific integrated circuits (ASICs), logiccircuits, and any other circuit or processor capable of executing thefunctions described herein. The above examples are example only, and arethus not intended to limit in any way the definition and/or meaning ofthe term “processor.”

As used herein, the terms “software” and “firmware” are interchangeable,and include any computer program stored in memory for execution by aprocessor, including RAM memory, ROM memory, EPROM memory, EEPROMmemory, and non-volatile RAM (NVRAM) memory. The above memory types areexample only, and are thus not limiting as to the types of memory usablefor storage of a computer program.

In one embodiment, a computer program is provided, and the program isembodied on a computer readable medium. In an exemplary embodiment, thesystem is executed on a single computer system, without requiring aconnection to a sever computer. In a further embodiment, the system isbeing run in a Windows® environment (Windows is a registered trademarkof Microsoft Corporation, Redmond, Wash.). In yet another embodiment,the system is run on a mainframe environment and a UNIX® serverenvironment (UNIX is a registered trademark of X/Open Company Limitedlocated in Reading, Berkshire, United Kingdom). The application isflexible and designed to run in various different environments withoutcompromising any major functionality. In some embodiments, the systemincludes multiple components distributed among a plurality of computingdevices. One or more components may be in the form ofcomputer-executable instructions embodied in a computer-readable medium.The systems and processes are not limited to the specific embodimentsdescribed herein. In addition, components of each system and eachprocess can be practiced independent and separate from other componentsand processes described herein. Each component and process can also beused in combination with other assembly packages and processes.

In some embodiments, registration of users for the care coordinationsupport platform includes opt-in informed consent of users to data usageby the smart home devices, wearable devices, mobile devices, autonomousvehicles, and/or smart vehicles consistent with consumer protection lawsand privacy regulations. In some embodiments, the user data, thecaregiver data, and/or other collected data may be anonymized and/oraggregated prior to receipt such that no personally identifiableinformation (PII) is received. In other embodiments, the system may beconfigured to receive user and caregiver data and/or other collecteddata that is not yet anonymized and/or aggregated, and thus may beconfigured to anonymize and aggregate the data. In such embodiments, anyPII received by the system is received and processed in an encryptedformat, or is received with the consent of the individual with which thePII is associated. In situations in which the systems discussed hereincollect personal information about individuals, or may make use of suchpersonal information, the individuals may be provided with anopportunity to control whether such information is collected or tocontrol whether and/or how such information is used. In addition,certain data may be processed in one or more ways before it is stored orused, so that personally identifiable information is removed.

As used herein, an element or step recited in the singular and proceededwith the word “a” or “an” should be understood as not excluding pluralelements or steps, unless such exclusion is explicitly recited.Furthermore, references to “exemplary embodiment” or “one embodiment” ofthe present disclosure are not intended to be interpreted as excludingthe existence of additional embodiments that also incorporate therecited features.

The patent claims at the end of this document are not intended to beconstrued under 35 U.S.C. § 112(f) unless traditionalmeans-plus-function language is expressly recited, such as “means for”or “step for” language being expressly recited in the claim(s).

This written description uses examples to disclose the disclosure,including the best mode, and also to enable any person skilled in theart to practice the disclosure, including making and using any devicesor systems and performing any incorporated methods. The patentable scopeof the disclosure is defined by the claims, and may include otherexamples that occur to those skilled in the art. Such other examples areintended to be within the scope of the claims if they have structuralelements that do not differ from the literal language of the claims, orif they include equivalent structural elements with insubstantialdifferences from the literal language of the claims.

We claim:
 1. A user computer device comprising at least one processor incommunication with at least one memory device, the user computer devicein communication with at least a second computer device, the at leastone processor of the user computer device programmed to: store userregistration information for a user associated with the user computerdevice; store caregiver registration information for a caregiverassociated with the user, wherein the caregiver registration informationincludes data for identifying the at least one second computer device;receive input from the user indicative of the user interacting with theuser computer device for a first time within a predefined period oftime; and in response to the user interaction, transmit a message to theat least one second computer device of the caregiver indicating that theuser has interacted with the user computer device during the predefinedperiod of time.
 2. The user computer device of claim 1, wherein thepredefined period of time starts after midnight and is until apredetermined time during the day.
 3. The user computer device of claim1, wherein the predefined period of time starts after midnight and isuntil a predetermined time in the morning of that day.
 4. The usercomputer device of claim 1, wherein the predefined period of time is a24 hour period.
 5. The user computer device of claim 1, wherein the atleast one processor is further programmed to: prompt the user within thepredefined period of time to interact with the user computer device,wherein the interaction includes at least one of the user (i) verballyresponding to the prompt, and (ii) clicking on a virtual buttondisplayed on a display device of the user computer device; and inresponse to the interaction with the user computer device by the user,transmit a message to the at least one second computer device of thecaregiver.
 6. The user computer device of claim 5, wherein the caregiverincludes one or more of a family member of the user, a friend of theuser, a paid caregiver of the user, a person designated by the user, anda healthcare professional.
 7. The user computer device of claim 5,wherein the at least one second computer device includes a plurality ofsecond computer devices, wherein each second computer device of theplurality of second computer devices is associated with a caregiver ofthe user.
 8. The user computer device of claim 7, wherein the at leastone processor is further programmed to transmit the message to theplurality of second computer devices.
 9. The user computer device ofclaim 1, wherein the at least one processor is further programmed todisplay, on a display device, one or more activities for the user for aparticular day.
 10. The user computer device of claim 1, wherein the atleast one processor is further programmed to communicate with at leastone server computer device to transmit messages to the at least onesecond computer device including the message to the at least one secondcomputer device of the caregiver indicating that the user has interactedwith the user computer device during the predefined period of time. 11.The user computer device of claim 1, wherein the at least one processoris further programmed to interact with the user in response to an audioprompt from the user.
 12. The user computer device of claim 1, whereinthe at least one processor is further programmed to: receive asubsequent input from the user; and transmit a notification messagebased on the subsequent input to the at least one second computerdevice, the notification message advising the caregiver of the at leastone second client device of the user's subsequent interaction with thefirst client device.
 13. The user computer device of claim 1, whereinthe at least one processor is further programmed to: store a pluralityof events for the user; and remind the user of an event of the pluralityof events.
 14. The user computer device of claim 13, wherein the atleast one processor is further programmed to audibly notify the user ofthe event.
 15. The user computer device of claim 13, wherein the atleast one processor is further programmed to transmit a message to theat least one second computer device that the user was reminded of theevent.
 16. The user computer device of claim 13, wherein the at leastone processor is further programmed to receive an acknowledgement of thereminder from the user.
 17. The user computer device of claim 16,wherein the at least one processor is further programmed to transmit amessage to the at least one second computer device that the user did notacknowledge the reminder.
 18. The user computer device of claim 13,wherein the at least one processor is further programmed to: receive asignal from an Internet of Things device associated with the event; andmark the event as complete based on the signal from the Internet ofThings device.
 19. The user computer device of claim 13, wherein the atleast one processor is further programmed to: determine an event wasmissed by the user; and transmit a notification to the at least onesecond computer device of the missed event.
 20. The user computer deviceof claim 13, wherein the at least one processor is further programmedto: receive an event from the at least one second computer device; andadd the event to the plurality of events for the user.
 21. The usercomputer device of claim 13, wherein the at least one processor isfurther programmed to notify the at least one second computer device ofcompleted events of the plurality of events.
 22. The user computerdevice of claim 1, wherein the user computer device comprises aplurality of computer devices associated with the user.
 23. The usercomputer device of claim 1, wherein the at least one processor isfurther programmed to: determine that the user has not interacted withthe user computer device for a predetermined period of time within thepredefined period of time; and transmit a message to the at least onesecond computer device that the user has not interacted with the usercomputer device for the predetermined period of time.